[Nagios-devel] nrpe RPM spec file bug(s)
Posted: Fri Dec 21, 2007 5:06 am
This is a multi-part message in MIME format.
------_=_NextPart_001_01C843D2.469FD40E
Content-Type: text/plain;
charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Hi,
=20
In the nagios spec file, the nagios user is added with command which creates a system account + system group.
=20
In the nrpe spec file, there is first a standard groupadd on the Nagios
group, and then a useradd with the -r option for the user.
It looks to me that the first groupadd is then useless, isn't it ?
=20
By the way : when the groupadd is run, there's a grep on the hardcoded
"nagios" value, while just after the %{nsgrp} is used to add the group,
which is also a bug I think...
=20
Nevertheless, if the groupadd has to be kept, would it be possible to
use it also with the "-r" option ? This way, a system group would be
created.
This would avoid conflicts with standard users/groups, and this would
also make things more consistent.
=20
I can easily patch the spec file, but I'm using nrpe on a few hundred
machines, and I guess other people managing clusters may face the same
problem of GID conflicts that I just did, which could probably be easily
be avoided.... so here I'm sharing the problem and potential solution.
=20
Thanks for patching && regards && merry Christmas ! :]
Frederic
------_=_NextPart_001_01C843D2.469FD40E
Content-Type: text/html;
charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Hi,
In the nagios spec file, the nagios user is =
added
with command « useradd –r » which creates a =
system
account + system group.
In the nrpe spec file, there is first a =
standard groupadd
on the Nagios group, and then a useradd with the –r option for the =
user.
It looks to me that the first groupadd is then =
useless,
isn’t it ?
By the way : when the groupadd is run, =
there’s
a grep on the hardcoded “nagios” value, while just after the =
%{nsgrp}
is used to add the group, which is also a bug I =
think…</fon
...[email truncated]...
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]
------_=_NextPart_001_01C843D2.469FD40E
Content-Type: text/plain;
charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Hi,
=20
In the nagios spec file, the nagios user is added with command which creates a system account + system group.
=20
In the nrpe spec file, there is first a standard groupadd on the Nagios
group, and then a useradd with the -r option for the user.
It looks to me that the first groupadd is then useless, isn't it ?
=20
By the way : when the groupadd is run, there's a grep on the hardcoded
"nagios" value, while just after the %{nsgrp} is used to add the group,
which is also a bug I think...
=20
Nevertheless, if the groupadd has to be kept, would it be possible to
use it also with the "-r" option ? This way, a system group would be
created.
This would avoid conflicts with standard users/groups, and this would
also make things more consistent.
=20
I can easily patch the spec file, but I'm using nrpe on a few hundred
machines, and I guess other people managing clusters may face the same
problem of GID conflicts that I just did, which could probably be easily
be avoided.... so here I'm sharing the problem and potential solution.
=20
Thanks for patching && regards && merry Christmas ! :]
Frederic
------_=_NextPart_001_01C843D2.469FD40E
Content-Type: text/html;
charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Hi,
In the nagios spec file, the nagios user is =
added
with command « useradd –r » which creates a =
system
account + system group.
In the nrpe spec file, there is first a =
standard groupadd
on the Nagios group, and then a useradd with the –r option for the =
user.
It looks to me that the first groupadd is then =
useless,
isn’t it ?
By the way : when the groupadd is run, =
there’s
a grep on the hardcoded “nagios” value, while just after the =
%{nsgrp}
is used to add the group, which is also a bug I =
think…</fon
...[email truncated]...
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]