Oh wow, after 3 days of trying to tweak other peoples scripts and make my own, all it took was to put the full paths like you said. Thanks so much!
Brian ________________________________ From: Alexander Malysh <[email protected]> To: Brian McCavour <[email protected]> Cc: "[email protected]" <[email protected]> Sent: Wednesday, January 30, 2013 4:23:12 AM Subject: Re: start-stop-daemon with --background flag or -d flag for bearebox Hi, you don't need start-stop-daemon and it's not supported/maintained anymore. Start bearerbox with a -d option BUT use full path, e.g.: /path/bearerbox -d /path/config.conf Alex Am 29.01.2013 um 18:54 schrieb Brian McCavour <[email protected]>: Hi, > > >Starting from the 1.4.3 source I configured/compiled: > >sh configure --enable-start-stop-daemon >make > > >Now when I run from utils/ > >./start-stop-daemon --start --exec ../gw/bearerbox -- >../kannel.config/kannel.conf >It works fine but executes in the shell. > > > >When I run with --backgorund it returns to the prompt and nothing happens. >./start-stop-daemon --start --background --exec ../gw/bearerbox -- >../kannel.config/kannel.conf >(Verified with lsof -i -n, as well as http admin interface fails to connect, >unlike the non "--background" attempt)) > > >Doing web search for a solution, I see many similar examples, though some use >run_kannel_box instead of directly calling the bearebox. >On further investigation I noticed that it's actualy the same result when I >simply run from gw/: > >./bearerbox ../kannel.config/kannel.conf (works fine) >and >./bearerbox -d ../kannel.config/kannel.conf (nothing happens) > > > >Does anyone know what I'm missing? > >Thanks, >Brian > > > > > > > > >
