No, because it is never chkconfig'ed on. The variable in /etc/default just keeps the init script from exiting when it is run, but nothing runs it. In other words, the ENABLED variable is just a failsafe, it can keep the init scripts from doing anything, but can't control whether they run at boot.
On Sep 14, 2012 5:32 PM, "Edison Su" <[email protected]> wrote: > In the cloud-early-config -> setup_vpcrouter: > enable_svc cloud-passwd-srvr 1 > then /etc/default/cloud-passwd-srvr should have ENABLED=1. > /etc/init.d/cloud-passwd-srvr should work then? > > > -----Original Message----- > > From: Marcus Sorensen [mailto:[email protected]] > > Sent: Friday, September 14, 2012 4:09 PM > > To: [email protected] > > Subject: Re: passwd server not set to start > > > > /etc/default controls variables for the /etc/init.d scripts. It looks > > like we're using /etc/default/cloud-passwd-srvr to override the > > 'ENABLED' variable in /etc/init.d/cloud-passwd-srvr. > > > > So there are two switches controlling services, in cloud-early-config > > we echo whether or not the script should be enabled into > > /etc/default/<scriptname>, and then in patchsystemvm.sh we actually > > turn on the service to start at boot. The service will exit and fail > > to start if the /etc/default file is set to do such. > > > > The ENABLED=1 is there in /etc/defaults, so we just need that stanza > > in patchsystemvm.sh to setup a vpc router. > > > > > I noticed that while looking in the config files. > > > > > > Take a look at /etc/default/cloud-passwd-srvr > > > or in source at: > > > patches/systemvm/debian/config/etc/default/cloud-passwd-srvr > > > > > > Keep in mind /etc/default in debian controls start on boot. > > > > > > --David >
