Re: wtmp locking problem (was: Re: SOLVED: Erk! Something is *really* wrong here!)
Craig Sanders:
> the more i think of it, the more it seems that there's a conflict
> between "Set A" and "Set B" login-related programs.
>
> "Set A" includes mgetty, telnet, getty, and other programs which call
> /bin/login. "Set B" includes ssh and wu-ftpd and other programs which do
> their own wtmp updating.
>
> Using only Set A programs on a system is fine. Using only Set B programs
> is fine too.
>
> Using both on the same system will cause the corruption.
This doesn't explain why the problems have only started occurring in the
past few days. I've been using the same set A/set B mix for many months, and
only started getting corruption this week. Something must have changed, and
that should be fixed.
--
#!/usr/bin/perl -i\$q='$q',\$p='$p';eval\$q.\$\^I\n"# # joey@kite.ml.org
$q='print"$p$^I\n',$p='#!/usr/bin/perl -i';eval$q.$^I # Joey Hess
"He. He. He." - - Herman Toothrot
Reply to: