Re: Help! Can't login or su, but SSH is ok... [solved]
The winbind entries were still in /etc/nsswitch.conf, but removing them didn't help. What did help was removing use_first_pass from /etc/pam.d/common-auth. Doh! Serves me right for trying to fix problems at the end of the day... Thanks for your pointer though, Kevin! I did have to clean up nsswitch.conf anyway, and doing so made me look up more about nsswitch.conf, where I found various examples that added use_first_pass to PAM config files. That's when I decided to try taking it out. Looking into it some more now, I realize that I was confusing use_first_pass's semantics with try_first_pass's. Indeed, with try_first_pass in common-auth things work just fine. Sigh... Marc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: Help! Can't login or su, but SSH is ok...
> -Original Message- > From: Marc Branchaud [mailto:[EMAIL PROTECTED] > Sent: Monday, January 22, 2007 2:54 PM > To: debian-user@lists.debian.org > Subject: Help! Can't login or su, but SSH is ok... > > Hi all, > > Over the weekend one of my sarge boxes decided to stop > accepting logins. > Currently, the box allows remote SSH (via public-key > authentication) > for regular users, but it doesn't allow user logins via > telnet or on the > console, even for root. SSH'd-in users also can't su to any user. > > The only way root can currently log in is to reboot in recovery mode. > Even in that mode, root can su to a regular user, but the > regular user > can't su. > > su reports: > su: Authentication information cannot be recovered > Sorry. > > On Friday, I did change the box's configuration. I had > previously been > trying to make it work with Samba Windows domain > authentication, and had > added some pam_winbind.so lines to files in /etc/pam.d/. On Friday I > decided that I didn't really need Windows domain auth, so I > removed all > references to pam_winbind.so from my /etc/pam.d/ files. > There were no > problems after the changes on Friday, though I wasn't overly > systematic > about trying things out, but I'm pretty sure I su'd to root... > > I can't figure out what went wrong. My /etc/pam.d/ files > look fine to > me (I can compare them to those on another, working sarge box on the > same network). I'm not even sure that's where the problem > lies. Google > can't tell me what "Authentication information cannot be recovered" > means, and the machine isn't logging anything when su or logins fail. Did you also make sure /etc/nsswitch.conf looks like the default? Namely, passwd, group, and shadow should all have "compat", and only "compat", in the second column. -- Kevin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Help! Can't login or su, but SSH is ok...
Hi all, Over the weekend one of my sarge boxes decided to stop accepting logins. Currently, the box allows remote SSH (via public-key authentication) for regular users, but it doesn't allow user logins via telnet or on the console, even for root. SSH'd-in users also can't su to any user. The only way root can currently log in is to reboot in recovery mode. Even in that mode, root can su to a regular user, but the regular user can't su. su reports: su: Authentication information cannot be recovered Sorry. On Friday, I did change the box's configuration. I had previously been trying to make it work with Samba Windows domain authentication, and had added some pam_winbind.so lines to files in /etc/pam.d/. On Friday I decided that I didn't really need Windows domain auth, so I removed all references to pam_winbind.so from my /etc/pam.d/ files. There were no problems after the changes on Friday, though I wasn't overly systematic about trying things out, but I'm pretty sure I su'd to root... I can't figure out what went wrong. My /etc/pam.d/ files look fine to me (I can compare them to those on another, working sarge box on the same network). I'm not even sure that's where the problem lies. Google can't tell me what "Authentication information cannot be recovered" means, and the machine isn't logging anything when su or logins fail. I'd appreciate at least some pointers as to how to debug this problem, cuz I'm stumped! Marc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: HELP!!!, can't login even as root
On Mon, 2004-11-22 at 23:54, Antonio Rodriguez wrote: [...] > I will need to use uploading of pictures in a website, and it seems to > me that this was the window used by (who/what)ever entered. Do you > have any recommendations about security measures related to this? > May creating some chroot environment, and then "file > pic" and make a decision from there, who knows. Any pointers to this > will be greatly appreciated. Check out the november 2004 issue (# 48) of linux magazine (https://www.linux-magazine.com/issue/48), it has an article on securing PHP scripts/servers which you might find interesting. Among other things it explains that "Safe_mode" isn't as safe as the name suggests. ATM the article isn't available online so I'll include the URL's of the article: [1] PHP documentation: http://www.php.net/docs.php [2] Manual on PHP security: http://de2.php.net/manual/de/security.index.php [3] Marc Heuse, "Installing a Secure Web Server": http://www.suse.de/de/private/support/online_help/howto/secure_webserv/ [4] Criticism of PHP safe_mode: http://ilia.ws/archives/18_PHPs_safe_mode_or_how_not_to_implement_security.html HTH Bram -- # Mertens Bram "M8ram" <[EMAIL PROTECTED]> Linux User #349737 # # SuSE Linux 8.2 (i586) kernel 2.4.20-4GB i686 512MB RAM # # 1:49pm up 10 days 4:32, 11 users, load average: 0.15, 0.23, 0.10 # -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Apache in a chroot (was: Re: HELP!!!, can't login even as root)
You might want to take a look at either mod_security (libapache-mod-security, libapache2-mod-security) or mod_chroot (libapache-mod-chroot) for the actual chroot. As for files, I use makejail, but if you only need mod_php, then you probably don't need to make any changes. If you need perl or mod_perl, than it gets much more complicated. As always, check google and tldp.org if you need more info. Antonio Rodriguez wrote: > I will need to use uploading of pictures in a website, and it seems to > me that this was the window used by (who/what)ever entered. Do you > have any recommendations about security measures related to this? > May creating some chroot environment, and then "file > pic" and make a decision from there, who knows. Any pointers to this > will be greatly appreciated. -- -BEGIN GEEK CODE BLOCK- Version: 3.1 GAT/CM$/CS>$/CC/IT$/M/S/O/U dpu s+:++ !a C++$>C+++$ UB+++>$L$*-- P+>++$ L+++()$ E-(---) W+++>$ N(+) o? K- w--(---) O? M V? PS++@ PE-@ Y+@ PGP++(+++)>$ t? 5? X? R tv--(-) b++(+++)@ DI? D? G e-> h* r? z* --END GEEK CODE BLOCK-- David Mandelberg [EMAIL PROTECTED] signature.asc Description: OpenPGP digital signature
Re: HELP!!!, can't login even as root
On Sun, Nov 21, 2004 at 05:02:43PM -0500, David Mandelberg wrote: > [EMAIL PROTECTED] wrote: > > the chroot step didn't work, rr webmail is being a pain, loging me out > > every 5 sec, sorry if send this mail twice, dont know if it made it > Hmm, it worked before though, are you sure you followed the exact same > steps (mkdir /mnt/debian, then mount /dev/ /mnt/debian, then > chroot /mnt/debian /bin/bash)? > > > is chroot indispensible for the dpkg reinstallation? > It's much easier with the chroot, but it's possible without chrooting. > > Just a brief overview on how chroot (the program not the C function) works: > 1. make some directory e.g. /mnt/debian the new root (/) for the current > process > 2. cd into / (/mnt/debian to the rest of the computer) > 3. run another program e.g. /bin/bash (/mnt/debian/bin/bash to the rest > of the computer) > > What that effectively does is put you 'in' your debian system even > though the computer is running knoppix. I will need to use uploading of pictures in a website, and it seems to me that this was the window used by (who/what)ever entered. Do you have any recommendations about security measures related to this? May creating some chroot environment, and then "file pic" and make a decision from there, who knows. Any pointers to this will be greatly appreciated. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: HELP!!!, can't login even as root
That h-thing is what, a code for what? :) http://catb.org/~esr/jargon/html/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: HELP!!!, can't login even as root
yeap, it is www-data. See next www-data:x:33:33:www-data:/var/www/:/bin/sh and www-data:x:33: It probably hapenned by allowing uploading of pictures through a perl script to my server without proper security. STUPID mistake, if it is the reason. And more stupid, if another mistake of mine. That h-thing is what, a code for what? Where can I read about this? Whats next step, wipe it all? What damage it could have done? Thank you guys for all. [EMAIL PROTECTED] wrote: > Access: (0660/-rw-rw) Uid: ( 33/www-data) Gid: ( 33/www-data) Do this: $ grep 33 /mnt/debian/etc/passwd $ grep 33 /mnt/debian/etc/group and email the user with uid 33 and the group with gid 33. If it actually is www-data/www-data, then you've probably been h4x0r3d, if it's bin/bin, then I'm just confused. Also, look around for a root-kit sniffer in knoppix and use it if you find one, this looks like either a break in or a really stupid mistake (no offense). -- -BEGIN GEEK CODE BLOCK- Version: 3.1 GAT/CM$/CS>$/CC/IT$/M/S/O/U dpu s+:++ !a C++$>C+++$ UB+++>$L$*-- P+>++$ L+++()$ E-(---) W+++>$ N(+) o? K- w--(---) O? M V? PS++@ PE-@ Y+@ PGP++(+++)>$ t? 5? X? R tv--(-) b++(+++)@ DI? D? G e-> h* r? z* --END GEEK CODE BLOCK-- David Mandelberg [EMAIL PROTECTED]
Re: HELP!!!, can't login even as root
[EMAIL PROTECTED] wrote: > Access: (0660/-rw-rw) Uid: ( 33/www-data) Gid: ( 33/www-data) Do this: $ grep 33 /mnt/debian/etc/passwd $ grep 33 /mnt/debian/etc/group and email the user with uid 33 and the group with gid 33. If it actually is www-data/www-data, then you've probably been h4x0r3d, if it's bin/bin, then I'm just confused. Also, look around for a root-kit sniffer in knoppix and use it if you find one, this looks like either a break in or a really stupid mistake (no offense). -- -BEGIN GEEK CODE BLOCK- Version: 3.1 GAT/CM$/CS>$/CC/IT$/M/S/O/U dpu s+:++ !a C++$>C+++$ UB+++>$L$*-- P+>++$ L+++()$ E-(---) W+++>$ N(+) o? K- w--(---) O? M V? PS++@ PE-@ Y+@ PGP++(+++)>$ t? 5? X? R tv--(-) b++(+++)@ DI? D? G e-> h* r? z* --END GEEK CODE BLOCK-- David Mandelberg [EMAIL PROTECTED] signature.asc Description: OpenPGP digital signature
Re: HELP!!!, can't login even as root
Ok, it seems someone got in, don't know, here goes what you asked me for: [EMAIL PROTECTED] mkdir /mnt/debian [EMAIL PROTECTED] mount -o rw,exec -t auto /dev/hdb1 /mnt/debian [EMAIL PROTECTED] chroot /mnt/debian /bin/bash chroot: cannot run command `/bin/bash': Permission denied [EMAIL PROTECTED] ls /mnt/debian bin cdrom flashcard lib mnt sbin tmp vmlinuz boot devfloppy lost+found proc stick usr vmlinuz.old card etchome memstickroot sysvar [EMAIL PROTECTED] file /mnt/debian/bin/bash /mnt/debian/bin/bash: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.2.0, dynamically linked (uses shared libs), stripped [EMAIL PROTECTED] [EMAIL PROTECTED] stat /mnt/debian/bin/bash File: `/mnt/debian/bin/bash' Size: 666892 Blocks: 1312 IO Block: 4096 regular file Device: 341h/833d Inode: 2681751 Links: 1 Access: (0660/-rw-rw) Uid: ( 33/www-data) Gid: ( 33/www-data) Access: 2004-11-21 17:02:04.0 -0500 Modify: 2004-11-11 01:42:13.0 -0500 Change: 2004-11-21 11:44:15.0 -0500 [EMAIL PROTECTED] [EMAIL PROTECTED] ls -l /mnt/debian/bin/bash -rw-rw 1 www-data www-data 666892 Nov 11 01:42 /mnt/debian/bin/bash Looks bad... Tell me guys, wipe all? David, thank you for all, same for Michael [EMAIL PROTECTED] wrote: > the chroot step didn't work, rr webmail is being a pain, loging me out every > 5 sec, sorry if send this mail twice, dont know if it made it Hmm, it worked before though, are you sure you followed the exact same steps (mkdir /mnt/debian, then mount /dev/ /mnt/debian, then chroot /mnt/debian /bin/bash)? > is chroot indispensible for the dpkg reinstallation? It's much easier with the chroot, but it's possible without chrooting. Just a brief overview on how chroot (the program not the C function) works: 1. make some directory e.g. /mnt/debian the new root (/) for the current process 2. cd into / (/mnt/debian to the rest of the computer) 3. run another program e.g. /bin/bash (/mnt/debian/bin/bash to the rest of the computer) What that effectively does is put you 'in' your debian system even though the computer is running knoppix. -- -BEGIN GEEK CODE BLOCK- Version: 3.1 GAT/CM$/CS>$/CC/IT$/M/S/O/U dpu s+:++ !a C++$>C+++$ UB+++>$L$*-- P+>++$ L+++()$ E-(---) W+++>$ N(+) o? K- w--(---) O? M V? PS++@ PE-@ Y+@ PGP++(+++)>$ t? 5? X? R tv--(-) b++(+++)@ DI? D? G e-> h* r? z* --END GEEK CODE BLOCK-- David Mandelberg [EMAIL PROTECTED]
Re: HELP!!!, can't login even as root
[EMAIL PROTECTED] wrote: > the chroot step didn't work, rr webmail is being a pain, loging me out every > 5 sec, sorry if send this mail twice, dont know if it made it Hmm, it worked before though, are you sure you followed the exact same steps (mkdir /mnt/debian, then mount /dev/ /mnt/debian, then chroot /mnt/debian /bin/bash)? > is chroot indispensible for the dpkg reinstallation? It's much easier with the chroot, but it's possible without chrooting. Just a brief overview on how chroot (the program not the C function) works: 1. make some directory e.g. /mnt/debian the new root (/) for the current process 2. cd into / (/mnt/debian to the rest of the computer) 3. run another program e.g. /bin/bash (/mnt/debian/bin/bash to the rest of the computer) What that effectively does is put you 'in' your debian system even though the computer is running knoppix. -- -BEGIN GEEK CODE BLOCK- Version: 3.1 GAT/CM$/CS>$/CC/IT$/M/S/O/U dpu s+:++ !a C++$>C+++$ UB+++>$L$*-- P+>++$ L+++()$ E-(---) W+++>$ N(+) o? K- w--(---) O? M V? PS++@ PE-@ Y+@ PGP++(+++)>$ t? 5? X? R tv--(-) b++(+++)@ DI? D? G e-> h* r? z* --END GEEK CODE BLOCK-- David Mandelberg [EMAIL PROTECTED] signature.asc Description: OpenPGP digital signature
Re: HELP!!!, can't login even as root
the chroot step didn't work, rr webmail is being a pain, loging me out every 5
sec, sorry if send this mail twice, dont know if it made it
is chroot indispensible for the dpkg reinstallation?
Thanks david
[EMAIL PROTECTED] wrote:
> Well, I did it, but it didn't help. Still unable to boot. The corresponding
> entry in fstab was changed to
> r,w,exec
That should be
rw,exec
If that doesn't fix it, try (in knoppix, after the chroot and mount -a):
# apt-get update
# apt-get install --reinstall `dpkg --get-selections \
| grep install | awk '{print $1};'`
note that this last command reinstalls everything on your system, so it
may take a while. also note that there are back-ticks and single-quotes
in there, so be carefull
If it still doesn't work, try these commands and email the output:
# apt-get install file # only if you don't already have it
# stat /bin/bash
# file /bin/bash
# ls -l /bin/bash
--
-BEGIN GEEK CODE BLOCK-
Version: 3.1
GAT/CM$/CS>$/CC/IT$/M/S/O/U dpu s+:++ !a C++$>C+++$
UB+++>$L$*-- P+>++$ L+++()$ E-(---) W+++>$ N(+) o? K-
w--(---) O? M V? PS++@ PE-@ Y+@ PGP++(+++)>$ t? 5? X? R tv--(-)
b++(+++)@ DI? D? G e-> h* r? z*
--END GEEK CODE BLOCK--
David Mandelberg
[EMAIL PROTECTED]
Re: HELP!!!, can't login even as root
[EMAIL PROTECTED] wrote:
> Well, I did it, but it didn't help. Still unable to boot. The corresponding
> entry in fstab was changed to
> r,w,exec
That should be
rw,exec
If that doesn't fix it, try (in knoppix, after the chroot and mount -a):
# apt-get update
# apt-get install --reinstall `dpkg --get-selections \
| grep install | awk '{print $1};'`
note that this last command reinstalls everything on your system, so it
may take a while. also note that there are back-ticks and single-quotes
in there, so be carefull
If it still doesn't work, try these commands and email the output:
# apt-get install file # only if you don't already have it
# stat /bin/bash
# file /bin/bash
# ls -l /bin/bash
--
-BEGIN GEEK CODE BLOCK-
Version: 3.1
GAT/CM$/CS>$/CC/IT$/M/S/O/U dpu s+:++ !a C++$>C+++$
UB+++>$L$*-- P+>++$ L+++()$ E-(---) W+++>$ N(+) o? K-
w--(---) O? M V? PS++@ PE-@ Y+@ PGP++(+++)>$ t? 5? X? R tv--(-)
b++(+++)@ DI? D? G e-> h* r? z*
--END GEEK CODE BLOCK--
David Mandelberg
[EMAIL PROTECTED]
signature.asc
Description: OpenPGP digital signature
Re: HELP!!!, can't login even as root
Well, I did it, but it didn't help. Still unable to boot. The corresponding
entry in fstab was changed to
r,w,exec
Even from the woody rescue cd couldn't get in, same response. Used a grub
floppy, tried to load another kernel, 2.4.20 i think, same response.
Any ideas what to do? Sunday, all are resting, bad luck for me.
Don't want to reinstall everything from scratch.
Hoping some ideas will pop from someones fingers.
Thank you David.
Try this from a knoppix xterm (or other terminal)
$ su
# mkdir /mnt/debian
# mount -o rw,exec -t auto /dev/ /mnt/debian
# chroot /mnt/debian /bin/bash
# mount -a
# /etc/fstab
make sure that / is mounting read-write and exec
[EMAIL PROTECTED] wrote:
> Running sid, computer went bananas. Gnome terminal
> froze. Logged out from X. Couldn't come back.
> Rebooteed. This is what happens:
>
> INIT: cannot excute "/etc/init.d/rcS"
> INIT: Entering runlevel:2
> INIT: cannot execute "/etc/init/d/rc"
> INIT: cannot execute "/usr/sbin/secvpnmon"
> same same same
> Id "SVPN" respawning too fast:
> disabled for 5 minutes
> (none) login: {I enter root}
> Password: {I enter root password}
> Unable to change tty /dev/tty1: Read-only file
> system.
> Cannot execute /bin/bash: Permission denied.
> Debian Gnu/Linux 3.1 (none) tty1
> (none) login:
> {I do again Control + Alt + Delete}
> Init: Switching to runlevel:6
> INIT: Sending processes the TERM signal
> INIT: Sending processes the KILL signal
> INIT: cannot execute "/etc/init.d/rc"
> Give root password for maintenance
> (or type Control-D to continue)
> {I enter root password}
> /bin/bash/: Permission denied
> /bin/sh: Permission denied
> Login incorrect
> Give root password for maintenance
> (or type Control-D to continue.
>
> After several of these cycles I give up, pull my
> Knoppix CD, boot from it, and from this yahoo
> account send this desperate SOS to my debian
> fellow users.
>
> A few mintes after, from webmail at rr i repeat
> the message. I think from the yahoo account it
> didn't make it.
>
>
--
-BEGIN GEEK CODE BLOCK-
Version: 3.1
GAT/CM$/CS>$/CC/IT$/M/S/O/U dpu s+:++ !a C++$>C+++$
UB+++>$L$*-- P+>++$ L+++()$ E-(---) W+++>$ N(+) o? K-
w--(---) O? M V? PS++@ PE-@ Y+@ PGP++(+++)>$ t? 5? X? R tv--(-)
b++(+++)@ DI? D? G e-> h* r? z*
--END GEEK CODE BLOCK--
David Mandelberg
[EMAIL PROTECTED]
Re: HELP!!!, can't login even as root
Try this from a knoppix xterm (or other terminal)
$ su
# mkdir /mnt/debian
# mount -o rw,exec -t auto /dev/ /mnt/debian
# chroot /mnt/debian /bin/bash
# mount -a
# /etc/fstab
make sure that / is mounting read-write and exec
[EMAIL PROTECTED] wrote:
> Running sid, computer went bananas. Gnome terminal
> froze. Logged out from X. Couldn't come back.
> Rebooteed. This is what happens:
>
> INIT: cannot excute "/etc/init.d/rcS"
> INIT: Entering runlevel:2
> INIT: cannot execute "/etc/init/d/rc"
> INIT: cannot execute "/usr/sbin/secvpnmon"
> same same same
> Id "SVPN" respawning too fast:
> disabled for 5 minutes
> (none) login: {I enter root}
> Password: {I enter root password}
> Unable to change tty /dev/tty1: Read-only file
> system.
> Cannot execute /bin/bash: Permission denied.
> Debian Gnu/Linux 3.1 (none) tty1
> (none) login:
> {I do again Control + Alt + Delete}
> Init: Switching to runlevel:6
> INIT: Sending processes the TERM signal
> INIT: Sending processes the KILL signal
> INIT: cannot execute "/etc/init.d/rc"
> Give root password for maintenance
> (or type Control-D to continue)
> {I enter root password}
> /bin/bash/: Permission denied
> /bin/sh: Permission denied
> Login incorrect
> Give root password for maintenance
> (or type Control-D to continue.
>
> After several of these cycles I give up, pull my
> Knoppix CD, boot from it, and from this yahoo
> account send this desperate SOS to my debian
> fellow users.
>
> A few mintes after, from webmail at rr i repeat
> the message. I think from the yahoo account it
> didn't make it.
>
>
--
-BEGIN GEEK CODE BLOCK-
Version: 3.1
GAT/CM$/CS>$/CC/IT$/M/S/O/U dpu s+:++ !a C++$>C+++$
UB+++>$L$*-- P+>++$ L+++()$ E-(---) W+++>$ N(+) o? K-
w--(---) O? M V? PS++@ PE-@ Y+@ PGP++(+++)>$ t? 5? X? R tv--(-)
b++(+++)@ DI? D? G e-> h* r? z*
--END GEEK CODE BLOCK--
David Mandelberg
[EMAIL PROTECTED]
signature.asc
Description: OpenPGP digital signature
HELP!!!, can't login even as root
Running sid, computer went bananas. Gnome terminal
froze. Logged out from X. Couldn't come back.
Rebooteed. This is what happens:
INIT: cannot excute "/etc/init.d/rcS"
INIT: Entering runlevel:2
INIT: cannot execute "/etc/init/d/rc"
INIT: cannot execute "/usr/sbin/secvpnmon"
same same same
Id "SVPN" respawning too fast:
disabled for 5 minutes
(none) login: {I enter root}
Password: {I enter root password}
Unable to change tty /dev/tty1: Read-only file
system.
Cannot execute /bin/bash: Permission denied.
Debian Gnu/Linux 3.1 (none) tty1
(none) login:
{I do again Control + Alt + Delete}
Init: Switching to runlevel:6
INIT: Sending processes the TERM signal
INIT: Sending processes the KILL signal
INIT: cannot execute "/etc/init.d/rc"
Give root password for maintenance
(or type Control-D to continue)
{I enter root password}
/bin/bash/: Permission denied
/bin/sh: Permission denied
Login incorrect
Give root password for maintenance
(or type Control-D to continue.
After several of these cycles I give up, pull my
Knoppix CD, boot from it, and from this yahoo
account send this desperate SOS to my debian
fellow users.
A few mintes after, from webmail at rr i repeat
the message. I think from the yahoo account it
didn't make it.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Help. Can't login
Ed Cogburn writes: > I'm begining to suspect that 1.3.28 was seriously broken too. I > downgraded to 1.3.26 from hamm, but 'plog -f' still doesn't work. It works here, on a straight hamm box. -- John Hasler [EMAIL PROTECTED] (John Hasler) Dancing Horse Hill Elmwood, WI
Re: Help. Can't login
Quoting [EMAIL PROTECTED] ([EMAIL PROTECTED]): > > Subject: Help. Can't login > Date: Mon, Oct 19, 1998 at 07:33:20AM -0400 > > In reply to:Victor Torrico > > Quoting Victor Torrico([EMAIL PROTECTED]): > > > > Running a pentium all slink box. Been working fine for months. > > > > Can't login when in console. It just stops at a blank line when I login and > > hit return. Runlevel 1 works OK. Xwindows comes up OK but "su" and "pon" > > wont work. They also stop at a blank line when I hit return. Control C > > gets the prompt back. > > > > Perplexing? Am dead in the water for now. > > > > Best regards. > > > > Victor > > > see post of Oct 18 titled > > sysklogd_1.3-29 is BROKEN was(Can't login as root) > and then downgrade sysklogd. > upgraded to -30 located in unstable at llug.sep.bnl.gov -30 seems to work fine. > -- > One good reason why computers can do more work than people is that they > never have to stop and answer the phone. > ___ > Wayne T. Topa <[EMAIL PROTECTED]> > >> Thanks for everyones help. -- Victor
Re: Help. Can't login
[EMAIL PROTECTED] wrote: > > Subject: Help. Can't login > Date: Mon, Oct 19, 1998 at 07:33:20AM -0400 > > In reply to:Victor Torrico > > Quoting Victor Torrico([EMAIL PROTECTED]): > > > > Running a pentium all slink box. Been working fine for months. > > > > Can't login when in console. It just stops at a blank line when I login and > > hit return. Runlevel 1 works OK. Xwindows comes up OK but "su" and "pon" > > wont work. They also stop at a blank line when I hit return. Control C > > gets the prompt back. > > > > Perplexing? Am dead in the water for now. > > > > Best regards. > > > > Victor > > see post of Oct 18 titled > > sysklogd_1.3-29 is BROKEN was(Can't login as root) > and then downgrade sysklogd. > I'm begining to suspect that 1.3.28 was seriously broken too. I downgraded to 1.3.26 from hamm, but 'plog -f' still doesn't work. -- Ed C.
Re: Help. Can't login
Subject: Help. Can't login Date: Mon, Oct 19, 1998 at 07:33:20AM -0400 In reply to:Victor Torrico Quoting Victor Torrico([EMAIL PROTECTED]): > > Running a pentium all slink box. Been working fine for months. > > Can't login when in console. It just stops at a blank line when I login and > hit return. Runlevel 1 works OK. Xwindows comes up OK but "su" and "pon" > wont work. They also stop at a blank line when I hit return. Control C > gets the prompt back. > > Perplexing? Am dead in the water for now. > > Best regards. > > Victor see post of Oct 18 titled sysklogd_1.3-29 is BROKEN was(Can't login as root) and then downgrade sysklogd. -- One good reason why computers can do more work than people is that they never have to stop and answer the phone. ___ Wayne T. Topa <[EMAIL PROTECTED]>
Help. Can't login
Running a pentium all slink box. Been working fine for months. Can't login when in console. It just stops at a blank line when I login and hit return. Runlevel 1 works OK. Xwindows comes up OK but "su" and "pon" wont work. They also stop at a blank line when I hit return. Control C gets the prompt back. Perplexing? Am dead in the water for now. Best regards. Victor
