Definition of the problem:
Installed applications daemons which have their startup scripts in
/usr/local/etc/rc.d/ are
not starting during system boot as they should.
Description of the problem:
I had very good working server at FBSD 5.2.1 with several applications (such
as apache2,
mysql,
The only daemon (called application somwhere in my mail) that starts normally during
system boot is apache2. Rest of them does not boot normally, but if I add them (I mean
'them' == the full path to their starting scripts in /usr/local/etc/rc.d/) to the end
of
apache`s script, then they are
On Wed, Jul 21, 2004 at 05:12:27PM -0600, Warren Block wrote:
On Wed, 21 Jul 2004, /root/of/all/evil wrote:
The only daemon (called application somwhere in my mail) that starts
normally during
system boot is apache2. Rest of them does not boot normally, but if I add
them (I mean
'them
I'm not sure we are talking about the same thing. Is the x
executable bit set when you do an ls -l in /usr/local/etc/rc.d?
# ls -l /usr/local/etc/rc.d
-r-xr-xr-x 1 root wheel635 Jun 15 05:58 apache.sh
^ ^ ^
Are these bits set for all of the scripts in the directory?
Definition of the problem:
Installed applications daemons which have their startup scripts in
/usr/local/etc/rc.d/ are
not starting during system boot as they should (only one script is starting - apache2).
Description of the problem:
I had very good working server at FBSD 5.2.1 with several