Subject: | |
From: | |
Reply To: | |
Date: | Tue, 7 Aug 2001 15:27:26 -0700 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Lars Appel wrote:
>
> Mike,
>
> >[2001/08/07 14:25:28, 0] locking/shmem_sysv.c:sysv_shm_open(601)
> > ERROR: root did not create the semaphore: semgid=107, rootgid=0
>
> This is just an oversight that can be ignored (the shared memory
> and semaphores will not be owned by UID=0 GID=0 on MPE/iX, they
> will be owned by the SMBD job user, eg SAMBA.ORG instead).
>
> >[2001/08/07 14:25:28, 0] locking/shmem_sysv.c:sysv_shm_open(622)
> > ERROR shmctl : can't IPC_SET. Error was Operation not permitted
> >[2001/08/07 14:25:28, 0] locking/locking.c:locking_init(174)
> > ERROR: Failed to initialise share modes
>
> These do not look healthy (ie my system does not have them ;-)
>
> Is it possible that IPCS.HPBIN.SYS -a shows some shared memory
> segments that are owned by a different user than the one that is
> now running the SMBD program? (eg manager.sys from past experiments
> or MGR.SAMBA from using the HP supplied 2.0.7 version). It might
> help to use IPCRM.HPBIN.SYS to remove those so SMBD can create (and
> own) fresh ones.
This also sort of sounds like maybe a job using shared memory got :ABORTJOB-ed,
and so the shared memory wasn't cleaned up, which causes problems for Samba
when trying to reuse the same shm id.
Always do a controlled shutdown of programs using shared memory or semaphores,
else you will need to learn how to use IPCS and IPCRM to clean up the mess left
behind by :ABORTJOB (or any other form of abnormal termination).
--
[log in to unmask]
Remainder of .sig suppressed to conserve scarce California electrons...
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
|
|