[nos-bbs] JNOS kill signal

Boudewijn (Bob) Tenty bobtenty at gmail.com
Mon Aug 8 18:53:23 EDT 2016

The best is to run jnos in a virtual console (tty) and that will already 
most likely restart (respawn) it if something happens.

I use SIGHUP if that freezes or if I want to restart it  after some 
changes in the autoexec.nos.

Use 'initctl to stop or start that tty. (Different command if you use 


On 2016-08-08 12:33 PM, Michael Fox - N6MEF wrote:
> Is there a preferred signal to send to JNOS to cause it to exit?
> Background:
> JNOS will occasionally hang/freeze (rare, but it happens).  I have a 
> watchdog script that will detect an unresponsive JNOS and restart it.  
> The conventional signal to send a process is SIGTERM, which will 
> typically cause a graceful exit.  One would expect the process to 
> close open files, remove lock files, etc.  But JNOS ignores SIGTERM.  
> I tried a few others:
> SIGHUP = not really a termination signal. Equivalent of user hang up.  
> But JNOS normally terminates with exit code 129
> SIGINT  = equivalent of CTRL-C.  JNOS normally terminates with exit 
> code 1.  I’ve been using this successfully.  But yesterday I had an 
> occasion where JNOS still didn’t terminate.
> SIGQUIT = equivalent of CTRL-\.  Typically, it terminates a process 
> and causes a core dump.  JNOS normally terminates with exit code 131.  
> But I don’t find a core dump anywhere.  (And I don’t know if Maiko 
> would find it helpful or not.)
> SIGKILL = most aggressive.  Cannot be trapped by the process.  JNOS 
> normally terminates with exit code 137
> I was going to adjust my script to try SIGINT first (since it has been 
> mostly successful so far) and, if it still won’t die, then try 
> SIGKILL.  But if the other signals are not handled any more 
> gracefully, then maybe it’s better to just send SIGKILL in the first 
> place.
> So, is there a preferred signal that will cause the most graceful 
> termination of JNOS or should I just send SIGKILL and be done with it.
> Michael
> _______________________________________________
> nos-bbs mailing list
> nos-bbs at tapr.org
> http://www.tapr.org/mailman/listinfo/nos-bbs

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/nos-bbs_lists.tapr.org/attachments/20160808/587fcee5/attachment.html>

More information about the nos-bbs mailing list