tisdag den 29 november 2011 klockan 19:42 skrev Robert Millan detta:
> Hi Mats,
>
> Is this problem specific to GNU/kFreeBSD? From the bug log I can't
> figure it out.
No, the problem is common to GNU/Linux and to GNU/kFreeBSD.
I can make no claim about GNU/Hurd. The implementation in Glibc
has progressed far since the time Xvt was contemporary, leaving
the code in "ttyinit.c" behind.
There are three issues at stake in this bug.
* ttyinit.c (write_utmp): Never sets "utent.ut_pid".
* ttuinit.c (write_utmp): Does not update WTMP_FILE,
only inserts a legacy item in UTMP_FILE.
* ttyinit.c (tidy_utmp): Does not update WTMP_FILE.
The structure element "ut_pid", and the system calls updwtmp(3)
and logwtmp(3) have all entered into Glibc after the time when
Xvt was last updated, so we should make use of them now.
Of probably neglectable effect, but good for consistency,
is a remedy of
* ttyinit.c (write_utmp): Does not initialise UTMP lookup
using setutent(3).
> AFAIK we use the same UTMP implementation as GNU/Linux, which comes
> from Glibc. I'd find it strange if this problem only happens in one
> of those platforms.
>
> However if the build system has miss-identified GNU/kFreeBSD as a BSD
> system, then it could be (wrongly) attempting to use BSD-style UTMP (I
> think this was called UTMPx).
The rules file forceably uses "-DLINUX" as compiler flag, thus it
does not detect kFreeBSD per se. This is only relevant to the CTTY
setting in #605679, though. In effect Hocevar's build system is
targeting exactly __GLIBC__, but has not been updated with the
present capacity of the library.
Nowadays Glibc also provides UTMPX, but the migration in Xvt would
need more effort than it is worth at the present time.
Best regards,
Mats E Andersson
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
