Strange behavior observed w.r.t 'su' command
Mr. Rullgard,
Confirmed. I have a Red Hat 9 system running 2.6.0-test11 with glibc 2.3.2-82 and coreutils 4.5.3-19.0.2. Killing su with SIGKILL does put the keyboard into unbuffered mode and does alternate the prompts. No error messages appear in dmesg.
Brad
=====
__________________________________
Do you Yahoo!?
Free Pop-Up Blocker - Get it now
http://companion.yahoo.com/
Quoted 4 lines · Bradley Chapman
Confirmed. I have a Red Hat 9 system running 2.6.0-test11 with glibc 2.3.2-82 and coreutils 4.5.3-19.0.2. Killing su with SIGKILL does put the keyboard into unbuffered mode and does alternate the prompts. No error messages appear in dmesg.
Does anyone know why redhat keeps doing these strange modifications? Over the years, I've encountered quite a few problems caused by redhat messing things up. A few examples:
- gcc 2.96
- A rather recent redhat version shipped with a broken 'sort' command. It performed a seemingly random permutation.
- Redhat 9 perl doesn't treat rexexps the same way a clean perl of the same version does.
Anyway, I guess it could be over soon, if only people would understand to stay away from that fedora stuff.
Signature · 2 lines
Måns Rullgård [email protected]
One more observation:
This time i wrote two shell functions, one for the user and another for root. I placed them in the .bash_profile
for rootz()
{
touch /tmp/createdbyroot
}
for userz()
{
touch /tmp/createdbyuser
}
I then reproduced the problem, and during the alternation of the prompts, when i was on the user prompt, i ran 'whoami' and it showed me as a normal user. Then i ran 'z'. I expected the filename in /tmp to be 'createdbyuser' but it is actually 'createdbyroot' !!!
/Raj