From: WANG Cong <xiyou.wangcong-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Halesh S <halesh.s-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [Patch] utmpname(3) returns int instead of void
Date: Sat, 28 Jun 2008 19:17:13 +0100 [thread overview]
Message-ID: <20080628181713.GA1605@hack.netcabo.pt> (raw)
As pointed by Halesh S, utmpname(3) should return int, just like what it is
in glibc's source code.
Signed-off-by: WANG Cong <wangcong-va7F5g4oNmbYtjvyW6yDsg@public.gmane.org>
Cc: Halesh S <halesh.s-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
---
Index: man-pages-3.01/man3/getutent.3
===================================================================
--- man-pages-3.01.orig/man3/getutent.3
+++ man-pages-3.01/man3/getutent.3
@@ -44,7 +44,7 @@ getutent, getutid, getutline, pututline,
.br
.B void endutent(void);
.sp
-.BI "void utmpname(const char *" file );
+.BI "int utmpname(const char *" file );
.SH DESCRIPTION
.BR utmpname ()
sets the name of the utmp-format file for the other utmp
@@ -116,6 +116,10 @@ and
return a pointer to a \fIstruct utmp\fP on success, and NULL on failure.
This \fIstruct utmp\fP is allocated in static storage, and may be
overwritten by subsequent calls.
+.br
+.BR utmpname()
+returns a value of 0 if the new name was successfully stored, and a
+value of -1 to indicate an error.
.SH FILES
/var/run/utmp database of currently logged-in users
.br
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2008-06-28 18:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-28 18:17 WANG Cong [this message]
[not found] ` <20080628181713.GA1605-E5McWMdeTmA/VrvnIVm4NQ@public.gmane.org>
2008-06-29 2:53 ` [Patch] utmpname(3) returns int instead of void Michael Kerrisk
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=20080628181713.GA1605@hack.netcabo.pt \
--to=xiyou.wangcong-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=halesh.s-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.