Re: /var/run/utmp
In article <cistron.19990314200005.B11176@rn082110.mrs.umn.edu>,
dan <dan@rn082110.mrs.umn.edu> wrote:
>For information about glibc2.1 and the new utmpd, please read the README.utmpd
>that comes with the glibc2.1 package.
I haven't installed glibc2.1 yet (just came back from CA), but I assume
now glibc implements /var/run/utmp and /var/run/utmpx like Solaris does
for backwards compatibility with libc5?
That's STUPID IMO. Debian has already dealt with this by making libc5
forwards compatible with libc6. If we are going to enforce this new
format we're going to break libc5 and libc6.0 apps AGAIN.
Also I do not like having to run yet another daemon (utmpd) to keep
2 files in sync (which in practice will get out of sync every so often
and break the system).
Can't we just keep things as they were? It must be possible to configure
glibc with --without-utmpd, right? Debian doesn't need the utmp/utmpx
monstrosity. Please.
Mike.
--
Indifference will certainly be the downfall of mankind, but who cares?
Reply to: