Yes, that fixed it. Now if I could just fix my typing. Sheesh.
Of course I couldn't just rebuild glibc. First I had to apply the fix
for http://sources.redhat.com/ml/libc-hacker/2005-12/msg00015.html, and
then resurrect the fix for
http://www.cygwin.com/bugzilla/show_bug.cgi?id=398, and _then_
I'm using /etc/shadow to authenticate passwords, what else?
Mark Post
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
John Summerfield
Sent: Sunday, September 24, 2006 7:19 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: OpenSSH Oddity
-snip-
If you're
I'm using /etc/shadow to authenticate passwords,
what else?
There are systems, even with shadow passwords enabled,
where 'pwconv' has yet to be run.
Doesn't seem like THAT would trip path_open(), but who can tell?
-- R;
--
Grand Day,
For Your Interest .on the Vendor's matter
We were running a PMR as Alan suggested and it was jogging along
quite well until Saturday.. On Saturday we switched from a z890 to a
z9-BC and our issue with QIOASSIST went away. So if you have a z890 and
issue with
On Friday 22 September 2006 17:48, Ranga Nathan wrote:
I am seeing these start-up errors:
Starting nfsboot (sm-notify) ..done
Importing Net File System (NFS)mount server reported tcp not
available, falling
back to udp
mount: RPC: Program not registered
mount server
Edmund R. MacKenty wrote:
On Friday 22 September 2006 17:48, Ranga Nathan wrote:
I am seeing these start-up errors:
Starting nfsboot (sm-notify) ..done
Importing Net File System (NFS)mount server reported tcp not
available, falling
back to udp
mount: RPC: Program not
Mark
FWIW, On my Intel based Linux server I had a very similar situation with
two different resolutions
1. did end up being a bad symlink to a lib, in my case even the symlink
did exist what was linked to did not so it caused this problem
2, This was really weird. and it's so windows like.
Post, Mark K wrote:
Ulrich, All,
Using GDB, I figured out that the S0C4 is coming from the path_open
routine of elf/dl-load.c in glibc. Is there any way to figure out which
assembler instructions belong to wchich lines of C source code? I don't
presume to be able to debug glibc, but at least
