From: Robert J. C. <rj...@gm...> - 2013-03-11 11:56:17
|
Marc, On Mon, Mar 4, 2013 at 11:24 PM, Marc MERLIN <ma...@me...> wrote: > On Mon, Mar 04, 2013 at 10:50:46PM -0500, Eloy Paris wrote: >> On 03/04/2013 07:38 PM, Robert J. Clay wrote: >> >> >On Sun, Mar 3, 2013 at 12:55 PM, Eloy Paris <pe...@ch...> wrote: >> > >> >>The only thing that lives outside these two locations is the MH init >> >>(upstart) script /etc/init/mh.conf. >> > >> > Which I would be most interested in taking a look at, if that's >> >possible; I'm not yet familiar with upstart as yet... >> >> My /etc/init/mh.conf is attached. MH starts on a "screen" session so I >> can attach to it to read messages sent to standard output or standard >> error by running "screen -r <user MH runs as>/". > > If you're doing do a debian package, please make a real one. Now, there's a rather provocative comment... > There is no reason to use upstart for this, over a normal initscript Why do you assume that I would have the package doing so? That it would be "over a normal initscript"? (Since packages from Debian already take advantage of the fact that upstart can handle a 'normal' initscript...) > and a package that will work for debian and ubuntu. Do keep in mind that upstart has been an option in Debian for some time... And in any case; using only an upstart init (not that I planned to do that) would not preclude it being usable in both, since upstart is in Debian. > Besides, people who know better run debian on servers, not ubuntu which is a > desktop bling distro :) You're not familiar with the Ubuntu Server Edition? I haven't used it myself recently, since I use pbuilder for package building & so don't actually need to have a ubuntu system for that, and Linux Containers (lxc) which uses debootstrap to create the file system. -- Robert J. Clay rj...@gm... |