Mailinglist Archive: opensuse-bugs (9407 mails)
| < Previous | Next > |
[Bug 343865] apache2 starts too early & fails bind due to missing interface on boot
- From: bugzilla_noreply@xxxxxxxxxx
- Date: Wed, 5 Mar 2008 02:37:19 -0700 (MST)
- Message-id: <20080305093719.1341A24538E@xxxxxxxxxxxxxxxxxxxxxx>
https://bugzilla.novell.com/show_bug.cgi?id=343865
User mt@xxxxxxxxxx added comment
https://bugzilla.novell.com/show_bug.cgi?id=343865#c11
Marius Tomaschewski <mt@xxxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
Info Provider|
|cd@xxxxxxxxxxxxxxxxx
Platform|x86 |All
--- Comment #11 from Marius Tomaschewski <mt@xxxxxxxxxx> 2008-03-05 02:37:18
MST ---
(In reply to comment #7 from C D)
OK, can you start this command:
(cd /etc/init.d && ls -1 rc?.d/* | sort) > /tmp/rc-link.list
and attach the /tmp/rc-link.list and /etc/init.d/.depend.start files?
It seems, that some of the links was modified manually (or using
some script adding them with ln -s) and the .depend.start file
(see also the startpar(8) manual page) does not reflect the start
order any more.
To reset to the default start/stop order of init-script the
command "insserv -d" can be used. From insserv manual page:
"[...]
-d, --default
Use default runlevels a defined in the scripts.
This may restore an edited runlevel link scheme.
[...]
[[/]path/to/init.d/]
Relative or absolute path to the init scripts base directory.
For the SuSE Linux boot concept, this defaults to /etc/init.d/
in compliance with the LSB specification. In this case insserv
does not add or remove a script to the runlevels declared in the
script headers, but may re-order the runlevels if the order of
the currently enabled scripts has changed (see option -d). Note
that if a relative path is used insserv has to be called from
the root directory.
[...]"
Note that every change in the LSB headers of the scripts its self
always requires the remove and re-install of the script. This
because insserv does not overwrite existing links as they can be
done by e.g. the runlevel editor. Only the option -d (for default)
will always overwrite any changes in the link scheme.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
User mt@xxxxxxxxxx added comment
https://bugzilla.novell.com/show_bug.cgi?id=343865#c11
Marius Tomaschewski <mt@xxxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
Info Provider|
|cd@xxxxxxxxxxxxxxxxx
Platform|x86 |All
--- Comment #11 from Marius Tomaschewski <mt@xxxxxxxxxx> 2008-03-05 02:37:18
MST ---
(In reply to comment #7 from C D)
The ifservices trick works for now. Thanks.
OK, can you start this command:
(cd /etc/init.d && ls -1 rc?.d/* | sort) > /tmp/rc-link.list
and attach the /tmp/rc-link.list and /etc/init.d/.depend.start files?
It seems, that some of the links was modified manually (or using
some script adding them with ln -s) and the .depend.start file
(see also the startpar(8) manual page) does not reflect the start
order any more.
To reset to the default start/stop order of init-script the
command "insserv -d" can be used. From insserv manual page:
"[...]
-d, --default
Use default runlevels a defined in the scripts.
This may restore an edited runlevel link scheme.
[...]
[[/]path/to/init.d/]
Relative or absolute path to the init scripts base directory.
For the SuSE Linux boot concept, this defaults to /etc/init.d/
in compliance with the LSB specification. In this case insserv
does not add or remove a script to the runlevels declared in the
script headers, but may re-order the runlevels if the order of
the currently enabled scripts has changed (see option -d). Note
that if a relative path is used insserv has to be called from
the root directory.
[...]"
Note that every change in the LSB headers of the scripts its self
always requires the remove and re-install of the script. This
because insserv does not overwrite existing links as they can be
done by e.g. the runlevel editor. Only the option -d (for default)
will always overwrite any changes in the link scheme.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
| < Previous | Next > |