- To: James Sadler <freshtonic@xxxxxxxxx>
- Subject: Re: [SLUG] git buildpackage
- From: Peter Chubb <peter.chubb@xxxxxxxxxxxx>
- Date: Fri, 21 May 2010 10:11:27 +1000
- Cc: slug@xxxxxxxxxxx
- Organization: National ICT Australia
- User-agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (Gojō) APEL/10.7 Emacs/23.2 (i486-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO)
>>>>> "James" == James Sadler <freshtonic@xxxxxxxxx> writes:
James> The application is an HTTP server to be launched on server
James> startup, so I used the init.d.ex and init.d.lsb.ex templates
James> generated by dh_make, removed the .ex extension and made sure
James> that the debian/rules file invoked dh_installinit. (also,
James> what's the reason for there being two init.d script flavours?)
James> The package is created successfully, but when the installation
James> starts the service the installation hangs. I'm guessing that I
James> have to control the daemonization of my service myself (I had
James> assumed that the boilerplate generated by dh_make or
James> start-stop-daemon would have taken care of it).
Does the process that starts daemonify itself? start-stop-daemon
assumes it's starting a daemon (i.e., a process that, after doing
whatever startup checks it needs to, forks and calls setsid() to
detach itself from its parent).
If you add a --background argument to start-stop-daemon, it'll do the
daemonification for you, but then you lose startup checks.
--
Dr Peter Chubb peter DOT chubb AT nicta.com.au
http://www.ertos.nicta.com.au ERTOS within National ICT Australia
All things shall perish from under the sky/Music alone shall live, never to die