It's strange how one can wake up and suddenly notice a pattern... Looking through the straces, and the disconnect timestamps of the SSH sessions, it seems that the processes are dying as soon as, or shortly after the SSH session is closed. My command is something along the lines of: java -cp /path/to/shared/libs/*:/path/to/class/directory/ path.to.MyApp > out.log 2>&1 & Does anyone have an idea as to why this process is closing when the SSH window that started it closes? Martin On 18 February 2011 09:47, Martin Hewitt <martin.hewitt at gmail.com> wrote: > Hi Cameron, > > On 18 February 2011 04:33, Cameron Kerr <cameron at humbledown.org> wrote: >> >> On 17/02/2011, at 9:35 PM, Mathieu Baudier wrote: >> >>>> I've been running our apps as purely as I can (java -cp >>>> /path/to/libs/* path.to.the.App) and they're still being send SIGHUP >>>> signals for reasons I can't understand. >>> >> >> I have only started in this thread, but your description of unexplainable SIGHUPs tweaked my memory from long ago, whereby it turned out to be bad memory. >> >> ... >> >> might be worth checking, stranger things have happened. >> >> Cheers, >> Cameron > > Thanks, but I've got these tests running on a couple of machines of > different generations, so I've ruled out the hardware as being at > fault. > > Martin > >> _______________________________________________ >> CentOS mailing list >> CentOS at centos.org >> http://lists.centos.org/mailman/listinfo/centos >> >