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