[imp] I've had it up to here.

[Chuck Cochems]

"Brent J. Nordquist" wrote:
> 
> On Thu, 20 Dec 2001, Chuck Cochems <zaphod@tdl.com> wrote:
> 
> > This is under a fairly new Linux glibc based system.
> 
> But you won't say which?  :-)  I'm trying to figure out what might be
> different between your system and all the other Linux systems that are
> working OK.
> 
> Does "ipcs -m" show any interesting patterns before/after the
> incorrect password is entered?  What do you do to clear the problem after
> it happens... and does "ipcs -m" show anything different before/after you
> clear it?  (I don't know a great deal about troubleshooting shm problems
> and that's been my main diagnostic tool.)
> 
root@bootp:~# ipcs -m

------ Shared Memory Segments --------
key        shmid      owner      perms      bytes      nattch    
status      
0x00000000 425984     root      600        1056768    9         
dest         
0x00000000 458753     nobody    600        46084      9         
dest         
0x00123754 65538      nobody    600        64000     
1                       

root@bootp:~# uname -a
Linux bootp 2.4.16 #1 SMP Sat Dec 1 16:15:00 PST 2001 i686 unknown

the ipcs output does not change at all, before or after the problem. ang
againnormal logins work.

Yes, i'm using the one that comes with horde.