From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/20110427/004208.html | 83 +++++++++++++++++++++++++++++++++ 1 file changed, 83 insertions(+) create mode 100644 zarb-ml/mageia-dev/20110427/004208.html (limited to 'zarb-ml/mageia-dev/20110427/004208.html') diff --git a/zarb-ml/mageia-dev/20110427/004208.html b/zarb-ml/mageia-dev/20110427/004208.html new file mode 100644 index 000000000..c888bce71 --- /dev/null +++ b/zarb-ml/mageia-dev/20110427/004208.html @@ -0,0 +1,83 @@ + + + + [Mageia-dev] How should an init script determine if it is being run during install or regular boot? + + + + + + + + + +

[Mageia-dev] How should an init script determine if it is being run during install or regular boot?

+ Olivier Blin + mageia at blino.org +
+ Wed Apr 27 14:11:42 CEST 2011 +

+
+ +
Michael scherer <misc at zarb.org> writes:
+
+>> While I can submit a new patch that checks to see
+>> if /var/lib/named or /mnt/var/lib/named exists, to
+>> determine if the script is running in an install or
+>> a normal bootup, I'm wondering if there is a "standard"
+>> way for an init script to determine which environment
+>> it's being run in.
+>
+> There is likely some heuristics based on env vars, but nothing
+> I can think of right now ( and that doesn't seems very good to 
+> react differently during installation or not ).
+
+You can use the following:
+
+if [ -z "$DURING_INSTALL" ]; then 
+  ...
+else
+  ...
+fi
+
+-- 
+Olivier Blin - blino
+
+ + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1