Voelker, Bernhard wrote:
Of course, why didn't I think of that? That's probably exactly what happened :) I'll give this a shot... I was thinking of first trying this with screen, which would do the same sort of thing.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. A useful feature addition for VBoxHeadless might be some sort of detach option for dummies like me to make this a little clearer. I was also playing around with doing something like: VBoxHeadless -s <VMname> > logfile.txt to keep a running log of what is printed to stdout, but this doesn't work. This might be handy if there are error messages and certainly for the useful notifications. One advantage of using screen will be being able to see the last few things outputted when I reattach a session. Is there some way that I'm not aware of to define log files for individual headless VMs? Have a nice day, Berny ------------------------------------------------------------------------------ _______________________________________________ VBox-users-community mailing list VBox-users-community@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vbox-users-community --
Joe Auty, NetMusician ![]() www.netmusician.org j...@netmusician.org |
------------------------------------------------------------------------------
_______________________________________________ VBox-users-community mailing list VBox-users-community@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vbox-users-community