![]() |
Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
I apologize for bringing up a Samba problem on a SCO system but I think it is primarily Samba related. I have been running Samba servers on both Linux and SCO Open Server ver 5.0.5a with no problems. I shut down both my SCO servers on New Years Eve. When I started them up again the next day Samba was not working. The daemons appear to load and remain running. The log.smb entry at this point is: [2000/01/08 14:11:25, 1] smbd/server.c:main(628) smbd version 2.0.5a started. Copyright Andrew Tridgell 1992-1998 [2000/01/08 14:11:25, 1] smbd/files.c:file_init(216) file_init: Information only: requested 10000 open files, 100 are available. Now when I try "smbclient -L myserver" I get the following response: Added interface ip=192.168.100.1 bcast=192.168.100.255 nmask=255.255.255.0 session request to MYSERVER failed session request to *SMBSERVER failed At this point the log file has: [2000/01/08 14:19:00, 0] locking/shmem_sysv.c:sysv_shm_open(597) ERROR: root did not create the semaphore [2000/01/08 14:19:00, 0] locking/locking.c:locking_init(174) ERROR: Failed to initialise share modes which is repeated again. I tried looking at the source code but not being a programmer it did not give me any clues. Essentially I am not seeing any STATUS..LCK or SHARE_MEM_FILE* files which would usually be created when I use the smbclient command. While writing this message today I restarted Samba on both my servers. On one I suddenly got a new message in the log.smb file: [2000/01/08 14:39:35, 0] lib/util_sock.c:open_socket_in(854) Get_Hostbyname: Unknown host scosysv.mydomain I changed the hostname in the /etc/hosts file to match the output of hostname (scosysv.mydomain), restarted Samba, and everything was ok on that machine. On my other SCO machine, /etc/hosts already matched the output of hostname so that one is still not working. Any ideas would be appreciated. --Frank - Subcription/unsubscription/info requests: send e-mail with "subscribe", "unsubscribe", or "info" on the first line of the message body to discuss-request at blu.org (Subject line is ignored).
![]() |
|
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |