Hi!
I'm using bacula-fd via inetd. This is an example line in inetd.conf:
bacula-fd stream tcp nowait root /usr/local/sbin/bacula-fd bacula-fd -i
-c /etc/opt/bacula/bacula-fd.conf
As you can see, I'm using the option -i as required for bacula's work
with inetd. This works well in "normal" cases, when all things alright:
The filedaemon is started for backup, it sends all data to storage daemon
an terminates correctly.
But, if I try to cancel a job using bconsole, the communication between
director and filedaemon fails. I found, that the director wants to
establish another connection to port 9102 (I guess, to send the cancel
command), and inetd then tries to start up a second process instance of
the filedaemon. This instance fails because it finds the pidfile of the
first, running backup instance.
The same thing works well if I run the filedaemon at front side.
Is this the expected behaviour? Or do I miss some option/directive.
The system is Solaris 9 with its own inetd. Or is this a general
limitation of inetd?
Regards,
Robert Wirth
--------------------------------------------------------
++ German Research Center for Artificial Intelligence ++
--------------------------------------------------------
Robert Wirth, Stuhlsatzenhausweg 3, D-66123 Saarbruecken
@office: +49-681-302-5078/5572 ++ @fax: +49-681-302-5341
mailto:[EMAIL PROTECTED] ++ http://www.dfki.de/~wirth
--------------------------------------------------------
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
