Thanks,
I spent the better part of the day trying to figure this one out. Not only did
I lose the ablilty to become root, but my machine hung when trying to start the
postgresql postmaster (which I believe needed root privlages). I was stumped
because I was able to boot up from my rescue disk and chroot to my system and
log in as root, but was not able to do it if I booted w/o the rescue disk. Do
you know how the sysklogd was able to stop all login's, su's and my postgre?
Bill
On Sat, 17 Oct 1998, Bob Nielsen wrote:
>The latest slink update to sysklogd 1.3-29 is SERIOUSLY broken. I
>installed it and could no longer become root. If you have installed it,
>you will need to boot with your rescue disk (you do have one, don't you?)
>and either disable sysklogd (chmod -x /etc/init.d/sysklogd) or install the
>hamm version.
>
>(Thanks to Alex Romosan for posting the chmod information on
>debian-devel).
>
>Bob
>
>----
>Bob Nielsen Internet: [EMAIL PROTECTED]
>Tucson, AZ AMPRnet: [EMAIL PROTECTED]
>DM42nh http://www.primenet.com/~nielsen
>
>
>--
>Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/nul
