[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: newly installed services, like mysql, not on by default after reboot?

Jeff Spaleta wrote:
> On Fri, Dec 12, 2008 at 12:57 PM, Mikkel L. Ellertson
> <mikkel infinity-ltd com> wrote:
>> I could have sworn that not turning on a service when it was
>> installed was the default. You are supposed to configure the new
>> service, and then turn it on.
> these sort of actions are done in the postinstall scriplets in the rpm
> packages.  You can check the logic  using rpm -q --scripts packagename
>    for any installed package.
> It should be realitively easy to confirm or disproof that there was or
> was not a logic change between F9 and F10. I just dont have an F9
> install handy to compare with for mysql or any other service.
> -jef
Only if using a stock config is does not pose a security problem.
The config file is included in the RPM. The postinstall script can
then activate the service. But it is a much better policy to let the
user activate the service them self. The exceptions are services
that do not accept connections from the outside world, and are
needed for system operation. (Cron, syslog, etc.)


  Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!

Attachment: signature.asc
Description: OpenPGP digital signature

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]