2009/5/30 Leslie Rhorer <[email protected]> > > > > -----Original Message----- > > From: [email protected] > > [mailto:nut-upsuser-bounces+lrhorer <nut-upsuser-bounces%2Blrhorer>= > [email protected]] > > On Behalf Of Manuel Wolfshant > > Sent: Saturday, May 30, 2009 4:23 AM > > To: 'NUT List' > > Subject: Re: [Nut-upsuser] This guy must be an idiot > > > > On 05/30/2009 06:09 AM, Leslie Rhorer wrote: > > > > > >> -----Original Message----- > > >> From: Charles Lepple [mailto:[email protected]] > > >> Sent: Friday, May 29, 2009 9:59 PM > > >> To: [email protected] > > >> Cc: NUT List > > >> Subject: Re: [Nut-upsuser] This guy must be an idiot > > >> > > >> What do the /etc/default/nut files look like on both systems? > > >> > > > > > > Yah, hello! I think you've found it. START_UPSD and START_UPSMON are > > both > > > set to "no" on the faulty machine. For the life of me I cannot > remember > > > ever editing this file on the working machine, though, so unless my > > memory > > > is just totally shot (a distinct possibility!), how is it the faulty > > machine > > > has these set to "no", and why would the distro do that in the first > > place? > > > > > I have no idea about the debian policy, but in fedora the default for > > all but "very mandatory" services is to install them in the "do not > > start by default" mode. Thus an admin MUST verify the config [, tune as > > needed if needed] and modify the service to turn it on by default. > > Speaking about nut, since an admin must select at least the driver and > > connection mode to be used, the approach of not starting by default > > looks valid to me. > > Well, I would argue that for any even remotely important system, a UPS and > its management utility would be "very mandatory". What's more, while > perhaps valid for user utilities, the thought process seems rather > backwards > for any system service. I suppose in the best of worlds, the package > maintainer would simply set the package to ask the installer if the service > should start automatically, as is the case with some packages I have > installed. It could also ask the name of the driver and connection mode. > > the problem here is that NUT *must* be configured before it can be started. more recent debs (ie 2.4.1, in jaunty, sid and testing) use the new nut.conf file, along with a rewritten init script that explicitly tells the user to configure nut. future release will provide a config tool...
cheers, Arnaud -- Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/
_______________________________________________ Nut-upsuser mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
