public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Thorsten Kukuk <kukuk@suse.de>
To: Ulrich Drepper <drepper@redhat.com>
Cc: libc-hacker@sources.redhat.com
Subject: Re: [PATCH] putgrent/putpwent and +/- entries
Date: Wed, 12 Jan 2005 09:35:00 -0000	[thread overview]
Message-ID: <20050112093513.GA31799@suse.de> (raw)
In-Reply-To: <41E49758.4040202@redhat.com>

On Tue, Jan 11, Ulrich Drepper wrote:

> Thorsten Kukuk wrote:
> 
> >putpwent and putgrent should not write a '0' as user/group id if an
> >entry starting with + or - is written. We have a check in the get*
> >code to ignore this, but it is better to not write the values and
> >let the fields empty.
> 
> I don't have a problem in principle with this but it needs to be 
> documented that user/group names starting with +- are everywhere treated 
> special.  Provide some text for the manual.


2005-01-12  Thorsten Kukuk  <kukuk@suse.de>

	* manual/users.texi (Writing a User Entry): Document behavior
	of putpwent if user name starts with + or -.

--- manual/users.texi	6 Apr 2002 01:01:48 -0000	1.34
+++ manual/users.texi	12 Jan 2005 09:33:20 -0000
@@ -1690,6 +1690,9 @@
 would inevitably leave out much of the important information.
 @c Then how are programmers to modify the password file? -zw
 
+This implementation leaves the group and user ID field empty if the
+group or user name starts with a - or +.
+
 The function @code{putpwent} is declared in @file{pwd.h}.
 @end deftypefun
 


-- 
Thorsten Kukuk         http://www.suse.de/~kukuk/      kukuk@suse.de
SuSE Linux Products GmbH       Maxfeldstr. 5       D-90409 Nuernberg
--------------------------------------------------------------------    
Key fingerprint = A368 676B 5E1B 3E46 CFCE  2D97 F8FD 4E23 56C6 FB4B

      reply	other threads:[~2005-01-12  9:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-11 10:55 Thorsten Kukuk
2005-01-12  3:22 ` Ulrich Drepper
2005-01-12  9:35   ` Thorsten Kukuk [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050112093513.GA31799@suse.de \
    --to=kukuk@suse.de \
    --cc=drepper@redhat.com \
    --cc=libc-hacker@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).