Ainsi parlait Michael Scherer :
> On Tuesday 05 August 2003 08:28, Frederic Lepied wrote:
> > David Walser <[EMAIL PROTECTED]> writes:
> > > If you didn't, please remove this rpmlint error:
> > > init-script-without-chkconfig-postin
> > >
> > > it's been discovered that not having the chkconfig-postin is the
> > > best way to have a service not set to start automatically upon
> > > installation (I discovered, Pixel agreed)
> >
> > Our policy is if a package is installed, it must be ready to run. So
> > we need to call %_post_service to follow this policy. What was the
> > original reason to make exceptions to this policy ?
>
> IIRc, it was for package who could not run out of the box, for some
> reasons.
> I didn't follow closely the thread, but, in fact, having some service
> started only for some occasion can be good.
>
> To give a example, honeyd is not really useful out of the box, since it
> need to determine on which ip address it should respond.
>
> and arpd can do a lot of trouble if launched by default, since it claims
> some ip address on the network.
>
> So, i guess that it should become a warning, and, some exception should
> be added.
%_post_service just add it to your current runlevel so as to be launched at
next boot, it doesn't run the service immediatly. You're free to configure it
correctly before.
I guess it's easier for a skilled admin to run chkconfig --del service after
installation if this default behaviour doesn't please him, than for a newbie
to understand why it doesn't work. Moreover, msec also allows you to disable
rpm call for chkconfig.
--
Guillaume Rousse
When you are in a hurry, the needle eye is always too small
-- Murphy's Laws of Sewing n�5
