Lee, Well I am assuming thats what the init script is there for. My bash skills are not great so I am not totally sure what the script is doing outside of editing the paths to the bin and pid files.
Nginx works fine when i start | restart | stop form the command line when i connected to the server. IT will release the terminal after running the command. When I access the server pages get get served and when I run htop i can see the process running. On Sep 8, 7:18 pm, Lee Hambley <[email protected]> wrote: > Stewart, quick sanity check - but you are telling nginx to daemonize, right > ? > > On 8 September 2010 17:42, Stewart <[email protected]> wrote: > > > > > Hello Again Lee, > > > Well i gotta admit i am really stumped on this one. The issue remains. > > Although its not a cap bug I thought I might update this post so > > anyone else that is having troubles might find it useful. > > > I have tried invoking bash in the command. That did not work. Same > > issue. > > I have tried nohup with the command. That did not work. > > I have tried 2 different startup scripts with nginx and that did not > > work. I am currently running the one at > >http://wiki.nginx.org/Nginx-init-ubuntu > > it seems to be the pick of them. > > I posted this issue in the ubuntu user forums. > >http://ohioloco.ubuntuforums.org/showthread.php?p=9816511with no > > replies to the post at the time of this writing. > > I have also posted to comp.security.ssh with out any answers either > > thread can be found here > >http://groups.google.com/group/comp.security.ssh/browse_thread/thread... > > Also I posted the issue on stack overflow for good measure > >http://stackoverflow.com/questions/3669216/ssh-not-releasing-terminal > > I have also asked in #ubuntu and #openssl on irc no solutions there > > either. > > > I will keep you updated if I find a solution to this. In the sort term > > the & and the end of the command ensures everything works. Its just > > not the best way to be doing things. > > > On Sep 7, 12:38 pm, Lee Hambley <[email protected]> wrote: > > > Stewart, I'm afraid I can't comment, but that's always a good way to > > > diagnose… in the event that you *really* don't care about what happens, > > you > > > can always suffix the command with a & (ampersand) > >http://hacktux.com/bash/ampersand--it will fork the process, and > > > background it - giving you back your terminal, but output wont be written > > > back to you. > > > > You might want to check #nginx and #openssh on Freenode IRC; it might > > also > > > be worth pastying your init scripts (what OS were you using?) - maybe > > > there's something weird in them, I'd be interested at least to take a > > look - > > > but I can hardly promise that I can help! > > > > - Lee > > > -- > > * You received this message because you are subscribed to the Google Groups > > "Capistrano" group. > > * To post to this group, send email to [email protected] > > * To unsubscribe from this group, send email to > > [email protected]<capistrano%2bunsubscr...@googlegrou > > ps.com>For more options, visit this group at > >http://groups.google.com/group/capistrano?hl=en -- * You received this message because you are subscribed to the Google Groups "Capistrano" group. * To post to this group, send email to [email protected] * To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano?hl=en
