On Wed, 2006-01-25 at 06:14, Martin Simmons wrote: > >>>>> On Tue, 24 Jan 2006 23:07:08 -0700, Robert W Hartzell <[EMAIL > >>>>> PROTECTED]> said: > > > > I've created a service manifest for the bacula file daemon on Solaris 10 > > 3/5 but it won't re-spawn the fd because I'm getting an exit status of > > 208 when killing or stopping the daemon. Anybody know what conditions > > could give an exit status of 208? I've run with debugging turned on but > > I'm not seeing any errors at -d600. Still searching the docs but haven't > > found anything related to the exit status. > > How is it being killed? Bacula normally exits with the signal number in > response to a kill. > > You could try attaching gdb to it and putting a breakpoint on exit. > > __Martin
Normal shutdown /opt/local/svc/support-files/bacula-fd stop I'm getting the same exit status for all the daemons on two systems that I have checked. This doesn't seem to effect bacula's operation but svc has to get an exit status of 0 or it puts the service into maintenance mode and it won't re-spawn the service without operator intervention. Thanks, Robert ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
