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

Bug#684732: unblock: nut/2.6.4-2



On Sun, Nov 11, 2012 at 22:43:42 +0100, Laurent Bigonville wrote:

> Le Sun, 11 Nov 2012 19:07:46 +0100,
> Julien Cristau <jcristau@debian.org> a écrit :
> 
> > On Sat, Sep 29, 2012 at 21:12:09 +0200, Laurent Bigonville wrote:
> > 
> > > Le Sat, 29 Sep 2012 20:56:11 +0200,
> > > Julien Cristau <jcristau@debian.org> a écrit :
> > > 
> > > > 
> > > > why is the last bit needed?
> > > > 
> > 
> > I didn't get a reply to the above (why you need adduser nut nut).
> 
> See #493159
> 
> This is to fix a situation were the user nut was not created without
> being added to the group. Is that correct Arnaud?
> 
Well that bug is marked as fixed in 2.2.2-7, which is way before
squeeze.  I suppose it can stay, it just seems useless.

> > 
> > > > +    if [ -d /var/run/nut ] ; then
> > > > +        chown root:nut /var/run/nut
> > > > +        chmod 770 /var/run/nut
> > > > +    fi
> > > > 
> > > > why does the nut user need write access there?  And why is this
> > > > created in postinst instead of an init script?
> > > 
> > > nut should be able to create sockets in that directory.
> > > 
> > > This is probably a bit redundant as this is also done in the
> > > initscript.
> > > 
> > Then I'd prefer to not have it in postinst.
> 
> Well this was a copy/paste of the nut-server postinstall script, so
> this should also be removed from that file too. Do you want me to do
> that for wheezy?

Please.

> The maintainer scripts should probably reworked a bit,
> but that will be for later I guess.
> 
Certainly not for right now indeed :)

Cheers,
Julien

Attachment: signature.asc
Description: Digital signature


Reply to: