From: Minty Date: 15:19 on 23 Jun 2006 Subject: init.d I want to start Apache2 on my Debian Sarge box to test something quick. I want to start it just this once for testing, then shut it down again. I do not want it to start on boot $ sudo /etc/init.d/apache2 start Not starting apache2 - edit /etc/default/apache2 and change NO_START to be 0. $ vi /etc/default/apache2 # 0 = start on boot; 1 = don't start on boot NO_START=1 1 != don't start on boot 1 = don't start
From: Paul Orrock Date: 15:32 on 23 Jun 2006 Subject: Re: init.d Minty wrote: > I want to start Apache2 on my Debian Sarge box to test something quick. > I want to start it just this once for testing, then shut it down again. > I do not want it to start on boot Fine, apache2 is set to not start on boot by default as you've discovered. > $ sudo /etc/init.d/apache2 start > Not starting apache2 - edit /etc/default/apache2 and change NO_START to > be 0. You're using the init (boot start up) system to try and start it as though it were being booted via init.d and it's rightly telling you "You've told me not to start on boot so I won't" What you want to do is start apache outside the boot system using the normal apache2ctl script Sorry to jump on your hate but ... Paul
From: Rafael Garcia-Suarez Date: 15:41 on 23 Jun 2006 Subject: Re: init.d On 23/06/06, Paul Orrock <paulo@xxxxxxxxxxxxxxxx.xxx> wrote: > > $ sudo /etc/init.d/apache2 start > > Not starting apache2 - edit /etc/default/apache2 and change NO_START to > > be 0. > > You're using the init (boot start up) system to try and start it as though it were being booted via init.d and it's rightly telling you "You've told me not to start on boot so I won't" > > What you want to do is start apache outside the boot system using the normal apache2ctl script But isn't this the purpose of the sys-v style initscripts to configure what to start and at which runlevel, without having to edit configuration files (with double negatives, yuck)... So, that debian-cumbersome-packaging-of-apache hate is justified.
From: imacat
Date: 16:17 on 23 Jun 2006
Subject: Re: init.d
--===[PGP/MIME_RFC2015]===449C05F4.7A37===
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
On Fri, 23 Jun 2006 16:41:09 +0200
"Rafael Garcia-Suarez" <rgarciasuarez@xxxxx.xxx> wrote:
> On 23/06/06, Paul Orrock <paulo@xxxxxxxxxxxxxxxx.xxx> wrote:
> But isn't this the purpose of the sys-v style initscripts to configure
> what to start and at which runlevel, without having to edit
1. Sys-V init scripts are for the boot process to start and stop.
2. Whoever run init scripts is acting as the boot process.
3. You told the boot process to skip it.
=> It is skipped.
Sys-V init scripts are plain text. You may read it yourself.
--
Best regards,
imacat ^_*' <imacat@xxxx.xxxxxx.xxx.xx>
PGP Key: http://www.imacat.idv.tw/me/pgpkey.txt
<<Woman's Voice>> News: http://www.wov.idv.tw/
Tavern IMACAT's: http://www.imacat.idv.tw/
TLUG List Manager: http://lists.linux.org.tw/cgi-bin/mailman/listinfo/tlug
--===[PGP/MIME_RFC2015]===449C05F4.7A37===
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
iEYEABECAAYFAkScBfQACgkQi9gubzC5S1wH4QCggt6UFl8vNsR+Y8p0BYHwb9Sm
P7IAn2NLxHwhab5GDYLSPSg+QOrY90zy
=eP0F
-----END PGP SIGNATURE-----
--===[PGP/MIME_RFC2015]===449C05F4.7A37===--
From: Rafael Garcia-Suarez Date: 16:24 on 23 Jun 2006 Subject: Re: init.d On 23/06/06, imacat <imacat@xxxx.xxxxxx.xxx.xx> wrote: > 1. Sys-V init scripts are for the boot process to start and stop. > 2. Whoever run init scripts is acting as the boot process. > 3. You told the boot process to skip it. > => It is skipped. That's precisely what's hateful: a superfluous configuration file that claims to know better than the initscript configuration per runlevel, and that gets in the way of getting the job done. A properly integrated apache should be startable and stoppable by calling the initscript with start/stop/restart (like every other service) without having to edit yet another obscure setting. (That said, I never used the Debian-bundled apache. So I don't feel the hate directly, only by proxy.)
From: A. Pagaltzis Date: 16:43 on 23 Jun 2006 Subject: Re: init.d * Paul Orrock <paulo@xxxxxxxxxxxxxxxx.xxx> [2006-06-23 16:35]: > You're using the init (boot start up) system to try and start > it as though it were being booted via init.d and it's rightly > telling you "You've told me not to start on boot so I won't" * imacat <imacat@xxxx.xxxxxx.xxx.xx> [2006-06-23 17:20]: > 1. Sys-V init scripts are for the boot process to start and > stop. > 2. Whoever run init scripts is acting as the boot process. > 3. You told the boot process to skip it. > => It is skipped. Err, have you two actually looked at the script in question? Whether or not to start a service at boot time is controlled by the regular hateful SysV symlink forest in `/etc/rc*.d`, but that is not what's going on here. The startup script in the Apache2 package of Debian includes an *additional* layer in the form of that `/etc/defaults/apache2` config option which determines whether the script will refuse to bring up Apache *regardless* of whether you have configured it to be brought up at boot time. I couldn't think of any reason why one would want to do something like that, so I dug into the package metadata. It appears that this is a lever used by the post-install script uses to castrate the boot script if port 80 is found to be occupied at package installation time. The mind boggles. This isn't hateful, it's insane. Regards,
Generated at 10:28 on 16 Apr 2008 by mariachi