Date: Tue, 12 Jun 2012 11:53:08 +0200 From: "Ronald Klop" <ronald-freebsd8@klop.yi.org> To: freebsd-stable@freebsd.org Subject: Re: su problem Message-ID: <op.wfsa2udz8527sy@ronaldradial.versatec.local> In-Reply-To: <CAEW%2BogZFeLSJ2ZERm4wsVSvwAzcSAZHJxQg5YQuGDBMPv2Tppg@mail.gmail.com> References: <CAEW%2BogYrUso=nqx4dUx0rhr9XUFMmSSMP-fxNa03pgj8tNF%2B%2Bg@mail.gmail.com> <201206091035.q59AZWFB058742@lurza.secnetix.de> <CAOgwaMvp4AyLNdvENL9rXoP6D6w9JaTJr1ML5uxb28Tg9=W2uQ@mail.gmail.com> <CAEW%2BogZ3H%2BgP86zcme-nuucLyDHmUo05uZ3R7Jc1hBb_7FM4gg@mail.gmail.com> <20120609122457.GS13609@albert.catwhisker.org> <CAEW%2BogadUQzu6k1XMXyLkqjEuq-_6gShiG5mRKbBgKMyoviAEg@mail.gmail.com> <20120609123626.GT13609@albert.catwhisker.org> <CAEW%2BogY4zZLj=D9cKuoG58Ozn_UbXjx3GJCT_Gtd4f4zEp3D2A@mail.gmail.com> <4FD37CF3.109@rdtc.ru> <op.wfqbt7hs8527sy@ronaldradial.versatec.local> <CAEW%2BogZFeLSJ2ZERm4wsVSvwAzcSAZHJxQg5YQuGDBMPv2Tppg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 11 Jun 2012 15:53:34 +0200, Sami Halabi <sodynet1@gmail.com> wrote: > Hi, > I opened 2 terminals with user sody. > in first i hit "su -", and supplied password, it was stcuked. > in the other I did: > > %ps xau | grep su > sody 39830 0.0 0.0 9124 1500 0 S+ 4:51PM 0:00.00 grep su > root 39812 0.0 0.0 21732 2088 1 I 4:49PM 0:00.00 su - > root 39813 0.0 0.0 21732 2108 1 I+ 4:49PM 0:00.00 su - > %procstat -kk 39812 > PID TID COMM TDNAME KSTACK > %procstat -kk 39813 > PID TID COMM TDNAME KSTACK > % > Mmmm, I'm out of options than. Maybe somebody else has a good idea. Ronald. > > Sami > > On Mon, Jun 11, 2012 at 11:14 AM, Ronald Klop > <ronald-freebsd8@klop.yi.org>wrote: > >> On Sat, 09 Jun 2012 18:42:27 +0200, Eugene Grosbein <egrosbein@rdtc.ru> >> wrote: >> >> 09.06.2012 19:47, Sami Halabi пишет: >>> >>>> %su - >>>> Password: >>>> load: 0.00 cmd: su 30588 [ttydcd] 0.91r 0.00u 0.00s 0% 2092k >>>> >>> >>> Perpaps, your system had no keyboard attached at boot time; >>> or for some other reason it booted with /dev/console being serial >>> console >>> instead of vidconsole. su locks trying to access serial console >>> that is /dev/ttyd0 by default and has Carrier Detect flag enabled. >>> Hence, it waits for CD on the first serial port (miserably and >>> hopelessly). >>> >>> You can check if it's true with "sysctl kern.console" command. >>> You could ask someone to boot the system with keyboard attached - >>> no need to type anything, though. The system should detect it >>> and assingn /dev/ttyv0 as /dev/console instead of /dev/ttyd0. >>> And "su" won't lock. >>> >>> Eugene Grosbein >>> >> >> >> Can you see what su is doing with procstat -kk <pid>? >> >> ______________________________**_________________ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/**mailman/listinfo/freebsd-**stable<http://lists.freebsd.org/mailman/listinfo/freebsd-stable>; >> To unsubscribe, send any mail to >> "freebsd-stable-unsubscribe@**freebsd.org<freebsd-stable-unsubscribe@freebsd.org> >> " >> > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?op.wfsa2udz8527sy>