glibc 2.3.2 => glibc 2.3.3 causes bash & syslog issues
 

Running Redhat 9 (Shrike) on AMD Athlon XP.

Updated glibc 2.3.2 => glibc 2.3.3 (all dependencies satisfied) and now have two interesting issues:

A) When executing bash or sh commands, I constantly get errors like:

-bash: child setpgid (3246 to 3246): No such process

This only appears to be cosmetic, but I'm skeptical that there's not some bigger problem. I've noticed this problem DOES NOT happen in a tcsh shell.

B) System Logger fails at startup, which caused startup to take forever. However, syslogd shows up in the process list once logged in, so maybe it's just hanging on something when it starts?

What I tried:

I tried updating Bash via a newer rpm, but that did nothing. I tried recompiling bash, but got "constant VIFWINDOW not defined" errors (if I remember correcty).

Questions:

1) WTF?

2) I installed glibc using i386 rpms. Could this have added to the problems, and should I have used something else (e.g. i686, athlon)?

3) Is this a lost cause? Should I just go back to glibc 2.3.2?

I've noticed other users in the forums with these exact issues and no resolution, so perhaps some wise guru can shed some light on issues like these once and for all ;)

Cheers,
Nate

Well, it's a week later, and in that time I've switched back to glibc 2.3.2 and all my problems are solved.

I guess the lesson is don't upgrade from glibc 2.3.2 to 2.3.3 unless you want to spent a lot of time rebuilding everything that comes with redhat 9.