retitle 289703 nessusd: Init.d script does not warn if nessusd didn't start properly severity 289703 wishlist thanks
On Tue, Jan 11, 2005 at 04:20:32PM +0100, Petr Nekula wrote: > Yes, that's the point. After running nessus-mkcert, everything is > running fine. > > Before running it ca_file variable was only in nessusd.conf.dkpg-old Then I guess you upgraded from an old version, were given the option to use the new nessusd.conf and overwrite yours (including your ca_file) > Maybe it should be good idea to include some warning into init.d script > and/or into /var/log/nessus/nessusd.messages . I'm not sure why it doesn't log to nessusd.messages (it should). But since nessusd cannot start without a proper configuration, I will probably introduce a check in the init.d script. Actually, I've been trying to find time to modify the preinst so that it will fold in this kind of automatic changes introduced by nessus-mkcert to a new nessusd.conf configuration file (if a different one is provided by the package). That's not as easy as it seems, however, and for the moment is something that the admin must do himself. > Thanks very much for your quick solution of this problem. No problem. Javier
signature.asc
Description: Digital signature
