On Jul 31, 12:21 am, Rainer Sokoll <[EMAIL PROTECTED]> wrote: > On Mon, Jul 30, 2007 at 07:11:26AM -0700, ajc wrote: > > > I'm having a problem where tracd locks up or doesn't work when I exit > > the console I started in. > > > I've installed the latest TRAC 0.11dev-r5879. Everything seems to > > install fine. I want to run with only the tracd server (no apache), > > so I log in to my machine as an end user over ssh and start trac in > > the background like this: > > > tracd -b mydomain.com --port 8000 \ > > --auth=myproject,/mypath/htdigest,myproject.mydomain.com \ > > /mypath/myproject & > > > Everything is great and I can access trac, everything works, I can > > access trac from external machines. The process is running in the > > background. > > > I then quit my ssh session and log out. TRAC is no longer accessible, > > and even though the process seems to be running the next time I log > > in, it no longer seems to be listening on port 8000. It stops > > listening on the port immediately when I log out. > > > Please help. > > ~ >whatis nohup > nohup nohup (1) - run a command immune to hangups
I'd initially also say nohup is needed as well, but if tracd is running the next time you log in, then nohup may not be the answer. Another thing that sometimes can cause problems with background processes started from an ssh session is where the application is outputing stuff to stdout/stderr, ie., you see output to your screen when logged in and start it. Now depending on how the ssh session was created, if that application keeps logging stuff to stdout/stderr after the ssh session is exited, it can in some cases eventually block on trying to write to stdout/stderr causing the process to hang. This would normally take a little while though as it has to fill up any output buffers first, thus wouldn't necessarily expect to see it stop working straight away. I'd also not expect it to stop listening on the port, instead it would just queue up pending socket connections until the listen queue filled up. Although at that point it would start refusing connections. Now whether tracd logs to stdout/stderr I don't know, but if it is and nohup doesn't fix your problem, trying redirecting output of tracd to a log file. tracd -b mydomain.com --port 8000 \ --auth=myproject,/mypath/htdigest,myproject.mydomain.com \ /mypath/myproject > /tmp/tracd.log 2>&1 & Graham --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
