Joe Auty wrote:
> I forgot to add that I started these processes via:
>
> VBoxHeadless -s <VMname> &
maybe the controlling terminal received a signal, e.g. when you logged
on to that server via ssh and a firewall closed that connection after a
timeout, then the shell and it's children would receive a SIGHUP and
die (unless a SIGHUP handler is defined).
In that case, you could try
nohup VBoxHeadless -s <VMname> &
Just a quick shot.
Have a nice day,
Berny
------------------------------------------------------------------------------
_______________________________________________
VBox-users-community mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/vbox-users-community
