I'm actually trying to monitor Kannel using monit, so I just made a simple start stop that runs *box with -d (finally works with full path) and pid-file, or kills the process. Hopefully it will work fine now, will be testing it soon. The only uncertainty I have right now is that kannel deleted the pid file when it shuts down / panics, and I am not sure if monnit is ok with that or not... hopefully. It seemed like such a simple thing to achieve after reading all the docs, but I became massively bogged down when -d wasn't working, and I tried to use run_kannel_box and start-stop-daemon.
Admittedly, I'm not the most qualified to be working on this, I've been a java client developer for 4 years, working in a windows environment. Jumping into a C project in linux is really the other side of the world for me. However it would still be nice if the user guide was updated to reflect the lack of support for that start-stop script. In 1.4.3 it says: After you have compiled Kannel and edited configuration file for your taste, you can either run Kannel from command line or use supplied start-stop-daemon and run_kannel_box programs to use it as a daemon service (more documentation about that later). Even documenting in the script header or something might be nice. Also including rpm spec files / build files that are used for various rpms would have saved me a few days as well :) In the end, its been a few weeks of learning, but I'm getting there thanks to some of you guys answering my many questions. Thanks again. Brian ________________________________ From: spameden <[email protected]> To: Brian McCavour <[email protected]> Cc: Alexander Malysh <[email protected]>; "[email protected]" <[email protected]> Sent: Wednesday, January 30, 2013 11:20:16 AM Subject: Re: start-stop-daemon with --background flag or -d flag for bearebox It all depends on the distribution you're using. On Debian it works just fine with start-stop-daemon from debian and special init.d script for kannel. For CentOS / Redhat it might a good idea to use supervised or something like that. Do not use start-stop-daemon script from kannel's source tree. Let me know if you need it I can share mine. 2013/1/30 Brian McCavour <[email protected]>: > > 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 > > > > > > > > >
