Displaying 2 results from an estimated 2 matches for "wtmpx_write".
Did you mean:
wtmp_write
2001 Jun 29
1
wtmpx problem on Solaris 8 sparcv9 (64bit) environment
...*li, struct utmpx *utx)
+#endif
{
log("utmpx_write_direct: not implemented!");
return 0;
@@ -1144,7 +1156,11 @@
/* write a wtmpx entry direct to the end of the file */
/* This is a slight modification of code in OpenBSD's logwtmp.c */
static int
+#ifdef __sparcv9
+wtmpx_write(struct logininfo *li, struct futmpx *utx)
+#else
wtmpx_write(struct logininfo *li, struct utmpx *utx)
+#endif
{
struct stat buf;
int fd, ret = 1;
@@ -1167,6 +1183,24 @@
return ret;
}
+#ifdef __sparcv9
+void
+utmpx_to_futmpx(struct utmpx *utx, struct futmpx *futx)
+{
+...
2004 Jul 08
1
openssh 3.8.1p1 problem on SCO 5.0.7
...sh 3.8.1p1, two entries are written to /etc/wtmp
and /etc/wtmpx each time a user logs in via ssh. This can be
demonstrated using the last(C) command. Any user connected via ssh will
have two identical login and logout entries.
On SCO, login_write() in loginrec.c calls both wtmp_write_entry() and
wtmpx_write_entry() (USE_WTMP and USE_WTMPX are defined).
wtmp_write_entry() writes the first entry to /etc/wtmp.
wtmpx_write_entry() ultimately calls updwtmpx() (HAVE_UPDWTMPX is
defined) to write the /etc/wtmpx entry. But updwtmpx() writes entries
to both the wtmp and wtmpx files on SCO, so now we have two...