Re: Systemd unit file implementation questions (ypbind)

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

 



On Thu, 14.04.11 12:55, Michal Hlavinka (mhlavink@xxxxxxxxxx) wrote:

> 
> On Thursday, April 14, 2011 09:54:59 Jóhann B. Guðmundsson wrote:
> > 
> > > Is there a good solution for this?
> > 
> > Which service ( file ) is this.
> > 
> > I can take a look at to see which way is best to approach it.
> 
> It's package nut : /etc/init.d/ups, there are 3 services: driver, upsd and upsmon.
> All three services usually run on the same machine, but it's not the only use case.
> There is going to be slight change for yet another use case. 
> Better not to get inspired by init script, but think about situation where there are
> three services and some/all of them should be started based on variable in config 
> file (so existing configuration works).

I think it is a good idea to enable/disable services only at once place,
the init system, instead of adding additional per-service layers of
disabling. An admin should not have to know how each service is
specifically configured in detail just to enable or disable it.

That means: if the admin enabels a service in systemd, the startup
script should not refuse starting just because it is disabled in another
config layer. That would be very confusing.

Lennart

-- 
Lennart Poettering - Red Hat, Inc.
-- 
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux