[Bug 222761] Re: [SRU] upsd doesn't start NOT 221737

2010-03-05 Thread Joatmon
A problem remains: Was having considerable difficulty installing NUT.
Same symptoms as above. That is:

u...@host:~$ sudo upsdrvctl start

resulted in:

Can't chdir to /var/run/nut: Permission denied
Driver failed to start (exit status=1)

After considerable difficulty I was convinced that I had compromised the
installation at which time I used Synaptic to remove NUT and then re-
install. Once again encountered the same issue. After much
searching/surfing I discovered this bug report. After executing

sudo usermod -G nut nut

NUT would run.

Configuration: Karmic, Belkin F6C900-UNV w/ USB interface.

-- 
[SRU] upsd doesn't start NOT 221737
https://bugs.launchpad.net/bugs/222761
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


Re: [Bug 222761] Re: [SRU] upsd doesn't start NOT 221737

2009-02-19 Thread Arnaud Quette
2009/2/18 Steve Beattie sbeat...@ubuntu.com

 I reproduced the problem with the original version of nut in the hardy
 release, 2.2.1-2.1ubuntu7, and confirmed that upgrading to the version
 in hardy-proposed, 2.2.1-2.1ubuntu7.2, corrected this issue. I also
 verified that things work properly when:

  - upgrading via 2.2.1-2.1ubuntu7 (release) - 2.2.1-2.1ubuntu7.1 (updates)
 - 2.2.1-2.1ubuntu7.2 (proposed)
  - installing 2.2.1-2.1ubuntu7.1 (updates) and upgrading to
 2.2.1-2.1ubuntu7.2 (proposed)
  - freshly installing 2.2.1-2.1ubuntu7.2 (proposed)

 Note that I (still) don't have a ups, so all I was able to verify was
 that upsdrvctl started up enough to get to the point that it failed when
 trying to talk to the (non-existent) serial device.


the dummy-ups driver is there to help you!
configure ups.conf with the following:
[myups]
driver = dummy-ups
port = test.dev

Copy the below file as /etc/nut/test.dev and relaunch your tests:
http://svn.debian.org/wsvn/nut/trunk/data/evolution500.dev?op=filerev=0sc=0

cheers,
Arnaud

-- 
[SRU] upsd doesn't start NOT 221737
https://bugs.launchpad.net/bugs/222761
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 222761] Re: [SRU] upsd doesn't start NOT 221737

2009-02-19 Thread Launchpad Bug Tracker
This bug was fixed in the package nut - 2.2.1-2.1ubuntu7.2

---
nut (2.2.1-2.1ubuntu7.2) hardy-proposed; urgency=low

  * debian/{nut-cgi,nut-hal-drivers,nut}.preinst: don't call adduser or
addgroup *at all*, these operations should be handled in the postinst.
Since this is the only custom action at all for nut-cgi and
nut-hal-drivers, remove those two preinsts completely.
  * debian/{nut-cgi,nut-hal-drivers,nut}.postinst: add nut to the dialout
and nut groups unconditionally, to handle the upgrade from the hardy
release.  LP: #222761
  * debian/control: nut needs Pre-Depends: debconf instead of Depends:,
because we use debconf unconditionally in the preinst.

 -- Steve Langasek steve.langa...@ubuntu.com   Fri, 23 Jan 2009
00:29:21 +

** Changed in: nut (Ubuntu Hardy)
   Status: Fix Committed = Fix Released

-- 
[SRU] upsd doesn't start NOT 221737
https://bugs.launchpad.net/bugs/222761
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 222761] Re: [SRU] upsd doesn't start NOT 221737

2009-02-18 Thread Steve Beattie
I reproduced the problem with the original version of nut in the hardy
release, 2.2.1-2.1ubuntu7, and confirmed that upgrading to the version
in hardy-proposed, 2.2.1-2.1ubuntu7.2, corrected this issue. I also
verified that things work properly when:

  - upgrading via 2.2.1-2.1ubuntu7 (release) - 2.2.1-2.1ubuntu7.1 (updates) - 
2.2.1-2.1ubuntu7.2 (proposed)
  - installing 2.2.1-2.1ubuntu7.1 (updates) and upgrading to 2.2.1-2.1ubuntu7.2 
(proposed)
  - freshly installing 2.2.1-2.1ubuntu7.2 (proposed)

Note that I (still) don't have a ups, so all I was able to verify was
that upsdrvctl started up enough to get to the point that it failed when
trying to talk to the (non-existent) serial device.

Thanks.

** Tags added: verification-done

** Tags removed: verification-needed

-- 
[SRU] upsd doesn't start NOT 221737
https://bugs.launchpad.net/bugs/222761
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 222761] Re: [SRU] upsd doesn't start NOT 221737

2009-01-29 Thread Launchpad Bug Tracker
This bug was fixed in the package nut - 2.2.2-10ubuntu3

---
nut (2.2.2-10ubuntu3) jaunty; urgency=low

  * debian/{nut-cgi,nut}.preinst: don't call adduser or addgroup *at
all*, these operations should be handled in the postinst.  Since
this is the only custom action at all for nut-cgi, remove that
preinst completely.
  * debian/{nut-cgi,nut}.postinst: add nut to the dialout
and nut groups unconditionally, to handle the upgrade from the hardy
release.  LP: #222761, LP: #287781.
  * debian/control: nut needs Pre-Depends: debconf instead of Depends:,
because we use debconf unconditionally in the preinst.
  * reinstate debian/nut-hal-drivers.postinst, which was lost in a
merge; and fix it up to use udevadm trigger --action=change, the
safe way to install udev rules.
  * have nut-hal-drivers Depend: on udev so it can use the above.
  * fix up nut postinst to also use 'udevadm trigger --action=change'

 -- Steve Langasek steve.langa...@ubuntu.com   Fri, 30 Jan 2009
01:06:53 +

** Changed in: nut (Ubuntu Jaunty)
   Status: Triaged = Fix Released

-- 
[SRU] upsd doesn't start NOT 221737
https://bugs.launchpad.net/bugs/222761
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 222761] Re: [SRU] upsd doesn't start NOT 221737

2009-01-27 Thread Steve Langasek
** Tags removed: verification-failed

-- 
[SRU] upsd doesn't start NOT 221737
https://bugs.launchpad.net/bugs/222761
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 222761] Re: [SRU] upsd doesn't start NOT 221737

2009-01-23 Thread Martin Pitt
Steve, that patch looks good to me, thank you! Please also apply it to
jaunty, and send it to Debian.

** Changed in: nut (Ubuntu Hardy)
   Status: In Progress = Fix Committed
   Target: ubuntu-8.04.3 = None

** Tags added: verification-needed

-- 
[SRU] upsd doesn't start NOT 221737
https://bugs.launchpad.net/bugs/222761
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 222761] Re: [SRU] upsd doesn't start NOT 221737

2009-01-23 Thread Steve Langasek
** Changed in: nut (Ubuntu Hardy)
   Target: None = ubuntu-8.04.3

-- 
[SRU] upsd doesn't start NOT 221737
https://bugs.launchpad.net/bugs/222761
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 222761] Re: [SRU] upsd doesn't start NOT 221737

2009-01-22 Thread Steve Langasek
** Changed in: nut (Ubuntu Hardy)
   Target: ubuntu-8.04.2 = ubuntu-8.04.3

-- 
[SRU] upsd doesn't start NOT 221737
https://bugs.launchpad.net/bugs/222761
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 222761] Re: [SRU] upsd doesn't start NOT 221737

2009-01-22 Thread Steve Langasek
** Changed in: nut (Ubuntu Hardy)
 Assignee: (unassigned) = Steve Langasek (vorlon)

-- 
[SRU] upsd doesn't start NOT 221737
https://bugs.launchpad.net/bugs/222761
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 222761] Re: [SRU] upsd doesn't start NOT 221737

2009-01-22 Thread Steve Langasek
I've uploaded a new version of nut to hardy-proposed which fixes several
serious issues with the maintainer scripts, this one chief among them.
Martin, please review and tell me if you think this is adequate.

I'll also check over the package's state in jaunty and prepare an upload
if necessary; I probably won't prepare a separate SRU for intrepid
unless there's specific demand.

-- 
[SRU] upsd doesn't start NOT 221737
https://bugs.launchpad.net/bugs/222761
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 222761] Re: [SRU] upsd doesn't start NOT 221737

2008-06-30 Thread Steve Langasek
With no other fixes available at this point, I'm copying nut
2.2.1-2.1ubuntu7.1 to hardy-updates so that users who install the
package fresh from 8.04.1 will have a working setup.  This bug is still
verification-failed and I'm not closing it, because we should still be
trying to deliver a working upgrade for users who already have the
package installed; re-targeting to 8.04.2 for that.

** Changed in: nut (Ubuntu Hardy)
   Target: ubuntu-8.04.1 = ubuntu-8.04.2

-- 
[SRU] upsd doesn't start NOT 221737
https://bugs.launchpad.net/bugs/222761
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 222761] Re: [SRU] upsd doesn't start NOT 221737

2008-06-13 Thread Martin Pitt
 if [ -z `getent group nut` ]; then
 addgroup --quiet --system nut
-#   else
-#   printf error: user \nut\ already exists... see 
/usr/share/doc/nut/README.Debian\nexit 1
+   else
+   printf skipping: user \nut\ already exists... see 
/usr/share/doc/nut/README.Debian\n
 fi
 }

Chuck, can you please explain how that changes the behavior? As far as I
can see, this patch just triggers an additional warning message to
appear (which is not good packaging, anyway; it will hardly be noticed).
Steve, what was the problem when you tested upgrade? Did the upgrade
fail (i. e. did addgroup error out because the group already existed),
or was the problem that an already existing nut user isn't in some
important group?

The nut user and group should *not* be removed on purging the package,
BTW. That's common and good Debian practice for daemons which create
files or processes owned by that system user. Otherwise the uid/gid
would be recycled on next adduser, and existing files/processes would
get owned by that new user.

-- 
[SRU] upsd doesn't start NOT 221737
https://bugs.launchpad.net/bugs/222761
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


Re: [Bug 222761] Re: [SRU] upsd doesn't start NOT 221737

2008-06-13 Thread Arnaud Quette
2008/6/13 Martin Pitt [EMAIL PROTECTED]:

 if [ -z `getent group nut` ]; then
 addgroup --quiet --system nut
 -#   else
 -#   printf error: user \nut\ already exists... see
 /usr/share/doc/nut/README.Debian\nexit 1
 +   else
 +   printf skipping: user \nut\ already exists... see
 /usr/share/doc/nut/README.Debian\n
 fi
  }

 Chuck, can you please explain how that changes the behavior? As far as I
 can see, this patch just triggers an additional warning message to
 appear (which is not good packaging, anyway; it will hardly be noticed).
 Steve, what was the problem when you tested upgrade? Did the upgrade
 fail (i. e. did addgroup error out because the group already existed),
 or was the problem that an already existing nut user isn't in some
 important group?


seconded. iirc, this fallback (nut already exist) should result in simply
checking if nut is already part of the dialout group (ie using a test -z
getent group dialout | grep nut) and adding it if it's not.

The nut user and group should *not* be removed on purging the package,
 BTW. That's common and good Debian practice for daemons which create
 files or processes owned by that system user. Otherwise the uid/gid
 would be recycled on next adduser, and existing files/processes would
 get owned by that new user.


irrc, I've removed the call to check_and_delete_user in {nut,nut-cgi}.postrm
for the uid/gid recycling, I've thought before about asking for fixed ones.
the only question is: a generic one (ups, power, ...) or a specific one
(nut)?

-- Arnaud


** Attachment added: unnamed
   http://launchpadlibrarian.net/15252044/unnamed

-- 
[SRU] upsd doesn't start NOT 221737
https://bugs.launchpad.net/bugs/222761
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


Re: [Bug 222761] Re: [SRU] upsd doesn't start NOT 221737

2008-06-13 Thread Steve Beattie
On Fri, Jun 13, 2008 at 06:32:27AM -, Martin Pitt wrote:
 Steve, what was the problem when you tested upgrade? Did the upgrade
 fail (i. e. did addgroup error out because the group already existed),
 or was the problem that an already existing nut user isn't in some
 important group?

The latter. If you installed the nut package from Hardy 8.04 and then
updated it to the package in -proposed, attempting to start upsdrvctl
would still fail with the same permission denied error. If the first
version of the package installed is the one in -proposed, then upsdrvctl
starts successfully. That's fine for going forward, but it leaves
people who have attempted to use the released package with their problem
unaddressed by the update. If that's sufficient for releasing an update,
then go ahead, I was just attempting to report the results I found.

Thanks.

-- 
Steve Beattie
[EMAIL PROTECTED]
http://NxNW.org/~steve/

-- 
[SRU] upsd doesn't start NOT 221737
https://bugs.launchpad.net/bugs/222761
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


Re: [Bug 222761] Re: [SRU] upsd doesn't start NOT 221737

2008-06-13 Thread Martin Pitt
Arnaud Quette [2008-06-13  7:35 -]:
 seconded. iirc, this fallback (nut already exist) should result in simply
 checking if nut is already part of the dialout group (ie using a test -z
 getent group dialout | grep nut) and adding it if it's not.

Please do if groups nut | grep -qw dialout, that's a little more
robust.

-- 
[SRU] upsd doesn't start NOT 221737
https://bugs.launchpad.net/bugs/222761
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 222761] Re: [SRU] upsd doesn't start NOT 221737

2008-06-13 Thread Martin Pitt
I rejected the current upload, since consensus now seems to be that the
current patch is not sufficient (and not necessary either).

-- 
[SRU] upsd doesn't start NOT 221737
https://bugs.launchpad.net/bugs/222761
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 222761] Re: [SRU] upsd doesn't start NOT 221737

2008-06-12 Thread Chuck Short
I believe I have addressed these issues in the most recent upload.

Thanks
chuck

-- 
[SRU] upsd doesn't start NOT 221737
https://bugs.launchpad.net/bugs/222761
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 222761] Re: [SRU] upsd doesn't start NOT 221737

2008-05-29 Thread Steve Beattie
I reproduced the initial problem using nut-2.2.1-2.1ubuntu7. I verified
that using the package in -proposed, nut-2.2.1-2.1ubuntu7.1, corrects
the issue, but *only* if the -proposed package is a new installation of
the nut package. Upgrading to the nut package in -proposed from the
version released in Hardy does not fix the issue; this is because the
nut user and group already exist in the passwd database, and thus
adduser does not get invoked. Similarly, removing the nut package
entirely and then attempting to install the fixed package leaves the
user with the same problem because on package removal the nut user and
group are not removed.

I'm assuming this is insufficient and am tentatively rejecting the fix,
as the committed fix doesn't actually address the issue for people
currently attempting to use the package.

My test system does not have a UPS attached so I haven't actually
verified that the nut package otherwise works.


** Changed in: nut (Ubuntu Hardy)
   Status: Fix Committed = In Progress

-- 
[SRU] upsd doesn't start NOT 221737
https://bugs.launchpad.net/bugs/222761
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 222761] Re: [SRU] upsd doesn't start NOT 221737

2008-05-29 Thread Martin Pitt
** Tags added: verification-failed

** Tags removed: verification-needed

-- 
[SRU] upsd doesn't start NOT 221737
https://bugs.launchpad.net/bugs/222761
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 222761] Re: [SRU] upsd doesn't start NOT 221737

2008-05-27 Thread Chuck Short
For those who were having problems can you enable hardy-proposed in your
/etc/apt/sources.list and try it out?

Thanks
chuck

-- 
[SRU] upsd doesn't start NOT 221737
https://bugs.launchpad.net/bugs/222761
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 222761] Re: [SRU] upsd doesn't start NOT 221737

2008-05-09 Thread Martin Pitt
Accepted into -proposed, please test and give feedback here

** Changed in: nut (Ubuntu Hardy)
   Status: Triaged = Fix Committed
   Target: ubuntu-8.04.1 = None

** Tags added: verification-needed

-- 
[SRU] upsd doesn't start NOT 221737
https://bugs.launchpad.net/bugs/222761
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 222761] Re: [SRU] upsd doesn't start NOT 221737

2008-05-06 Thread Martin Pitt
Please test your changes...

$ sudo adduser --quiet --system nut --home /var/lib/nut --no-create-home nut
adduser: Specify only one name in this mode.

I guess you want

  adduser --quiet --system --group --home /var/lib/nut --no-create-home
nut

-- 
[SRU] upsd doesn't start NOT 221737
https://bugs.launchpad.net/bugs/222761
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 222761] Re: [SRU] upsd doesn't start NOT 221737

2008-05-06 Thread Chuck Short

** Attachment added: Diff
   http://launchpadlibrarian.net/14256483/diff

-- 
[SRU] upsd doesn't start NOT 221737
https://bugs.launchpad.net/bugs/222761
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 222761] Re: [SRU] upsd doesn't start NOT 221737

2008-05-05 Thread Chuck Short

** Attachment added: Fixed diff
   http://launchpadlibrarian.net/14225619/diff

-- 
[SRU] upsd doesn't start NOT 221737
https://bugs.launchpad.net/bugs/222761
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 222761] Re: [SRU] upsd doesn't start NOT 221737

2008-05-02 Thread Steve Langasek
** Changed in: nut (Ubuntu)
   Target: ubuntu-8.04.1 = None

** Changed in: nut (Ubuntu Hardy)
   Importance: Undecided = Medium
   Status: New = Triaged
   Target: None = ubuntu-8.04.1

-- 
[SRU] upsd doesn't start NOT 221737
https://bugs.launchpad.net/bugs/222761
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


Re: [Bug 222761] Re: [SRU] upsd doesn't start NOT 221737

2008-04-29 Thread Al Grimstad
On Tue, 2008-04-29 at 07:41 +, Martin Pitt wrote:
 Chuck, that looks much better already. However, the changelog says nut
 group, whereas the patch puts the nut user into dialout. Which one is
 right and intended?

This comment suggests that a fix to the problem is adding the user nut
to the group dialout. Do I understand correctly?

I had done this already to handle permissions on the port my UPS was
attached to. That is, the owner.group for /dev/ttyS0 is root.dialout and
so to get nut to work one has to do an adduser nut dialout.

Doing an adduser nut nut, which fixes the problem, seems to me to be a
hack, not a proper fix. I ask again, when the code was built, was the
argument -with-user=nut given to configure?

-- 
[SRU] upsd doesn't start NOT 221737
https://bugs.launchpad.net/bugs/222761
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 222761] Re: [SRU] upsd doesn't start NOT 221737

2008-04-29 Thread Rick Clark
** Changed in: nut (Ubuntu)
   Importance: Undecided = Medium
   Target: None = ubuntu-8.04.1

-- 
[SRU] upsd doesn't start NOT 221737
https://bugs.launchpad.net/bugs/222761
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 222761] Re: [SRU] upsd doesn't start NOT 221737

2008-04-28 Thread Chuck Short
** Summary changed:

- upsd doesn't start NOT 221737
+ [SRU] upsd doesn't start NOT 221737

-- 
[SRU] upsd doesn't start NOT 221737
https://bugs.launchpad.net/bugs/222761
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 222761] Re: [SRU] upsd doesn't start NOT 221737

2008-04-28 Thread Martin Pitt
+# Make sure that the nut group actually exists
+adduser nut nut

First, the comment and command do not match. This will *not* create a
nut group. Second, this is missing a test whether both the user and the
group have a system ID (100 = id  500). Third, this call looks really
weird in the first place. How is this system user created? The standard
way to do this is adduser --system nut --group --no-create-home, which
will take care of properly creating the system group as well.

-- 
[SRU] upsd doesn't start NOT 221737
https://bugs.launchpad.net/bugs/222761
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs