Definition of the problem:
Installed applications daemons which have their startup scripts in
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
mysql, pureftpd, postfix, saslauth) and I have upgraded it one day, due to
of FBSD developers, and application advisories due to portaudit advisories.
Buildworld and whole process of upgrading system from cvsup goes well,
portupgrade of applications
also. And after that I discovered, that upgraded applications does not start
during system boot.
I chcecked my srcipts permissions (fine), same scripts (fine too - if I run
any script from
commandline after the system start, it boots the proper daemon nicely) and
config files of
applications (fine too).
After that I started to read forums, and google, then find out that daemons
now needs declarations
in /etc/rc.conf so I added them. Still nothing. I finished with that I added
the scripts at the end
of the only starting script which is apache2 script, but this is *NOT*
proper solution, even
if daemons are working.
Can *anybody* give me *any* hint/tip or tell me what I did wrong? Im fightng
with that for almost
two weeks right now, and that affects all 3 of my machines.
sample startup script from .../rc.d/:
# PROVIDE: pureftpd
# REQUIRE: NETWORKING SERVERS
# BEFORE: DAEMON
# KEYWORD: FreeBSD shutdown
# Add the following lines to /etc/rc.conf to enable pure-ftpd:
Please, give me any help, if you know what is going on here.
Thanks a lot, r.
Message sent using UebiMiau 2.7.2
[EMAIL PROTECTED] mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"