Re: [hylafax-users] Blocked by concurrent cal

[Lee Howard <faxguy@xxxxxxxxxxxxxxxx>]

Tony Delov wrote:

> Also. I was using the
>    /etc/init.d/hylafax stop ;   /etc/init.d/hylafax start
> script to stop and start the server.
> We have a busy server and I was wondering how safe it is to actually 
> stop and start the server?
> Is there any reason that the start up script doesn't have a "reload" 
> or "restart" option?
> Perhaps I should use a kill -HUP [hfaxd PID] instead next time? 


Most init "restart" scripts are simply a "stop+start".

Generally speaking stopping hfaxd and faxq alone will be safe enough.  
faxq won't exit anyway until all of the faxsend jobs exit first.

Restarting hfaxd is generally not a problem at any time.  Restarting 
faxq should not be done until the previous faxq exits... otherwise 
you'll end up with two faxqs running and competing and making a mess.

Any faxsend process should usually be stopped by an abort (like 'faxrm') 
command.  Killing them in the middle of fax sessions will likely result 
in losing the jobs.  Likewise faxgetty should not be stopped in the 
middle of a fax session (or there likely will be issues with that fax 
image data)... a 'faxabort' can usually get it aborted, if needed.

The HylaFAX RPMs that have been around forever do have a restart 
option... it's just a stop+start.  The problem with that is that it 
doesn't take into account faxsend processes (it doesn't shut them down) 
and doesn't always wait for faxq to exit before starting it up again.  
Also, it tends to "killall faxgetty" but that also isn't exactly 
gentle.  There are gentle ways to automate all of that, but I don't know 
that anyone's contributed a replacement init script.

Lee.


____________________ HylaFAX(tm) Users Mailing List _______________________
 To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null
 *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*