2009/2/18 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:
>
> - upgradi
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
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
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\n" && exit 1
> + else
> +
both!
the aim is to keep nut in the nut group (which is the base for the
framework to operate) and to add it to the dialout group to solve the
need of user action for accessing serial devices.
as I state in the README.Debian, USB devices access is already handled
via udev...
-- Arnaud
--
[SRU]
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
