This is a multi-part message in MIME format.
------_=_NextPart_001_01CA259C.405697FE
Content-Type: multipart/alternative;
boundary="----_=_NextPart_002_01CA259C.405697FE"
------_=_NextPart_002_01CA259C.405697FE
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Dears,
=20
Attached is a small patch that hopefully you'll take into account.
Its purpose is just to unify NRPE's way of creating nagios user and
group : it is currently creating a system user (using the -r option),
but a standard group (without the -r option)...
=20
So I changed that in the attached patch, and changed a bit the comments
in order to reflect this.
I hope you'll welcome this, but at least you'll be aware of the problem.
=20
Some background for this simple patch :
This is actually a problem for us, because we're installing nrpe on lots
of nodes which contain *lots* of local accounts, all created with a
pre-defined and unified (i.e : same on all hosts) UID/GID.
But when we add users after NRPE was installed, we sometimes run into
the situation when nagios GID is in fact using a GID we'd like to deploy
- and of course if we could be sure RPM install would guarantee the
nagios GID would be
Dears,
Attached is a small patch that =
hopefully you’ll
take into account.
Its purpose is just to unify =
NRPE’s
way of creating nagios user and group : it is currently creating a =
system user
(using the –r option), but a standard group (without the –r =
option)…
So I changed that in the =
attached patch,
and changed a bit the comments in order to reflect =
this.
I hope you’ll welcome =
this, but at
least you’ll be aware of the problem.
Some background for this simple =
patch :
This is actually a problem for =
us, because
w
...[email truncated]...
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]