search for: share_mem_file

...UNIX, so they are simulated using shared memory, or lock files if your UNIX doesn't support shared mem- ory (almost all do). Yet I have these files on my (RedHat v6.0 / kernel v2.2.10) system: # ls -l /var/lock/samba total 12 -rw-r--r-- 1 root root 1048576 Jul 8 14:51 SHARE_MEM_FILE -rw-r--r-- 1 root root 12 Jul 8 14:53 SHARE_MEM_FILE.processes -rw-r--r-- 1 root root 4000 Jul 8 14:57 STATUS..LCK -rw-r--r-- 1 root root 231 Jul 8 16:49 browse.dat -rw-r--r-- 1 root root 20 Jul 6 18:41 nmbd.pid -rw-r--r-- 1 root...

I've encountered a new problem that occurred during installation. It happened identically on new installs for both Caldera OpenLinux 2.2 and Red Hat 6.0. These files did not get created: SHARE_MEM_FILE, SHARE_MEM_FILE.processes, and STATUS..LCK. I'm using the smb.conf from another working system that has the identical share layout. The default Samba install was 2.0.3 for both distributions. I tried upgrading and even removing and reinstalling 2.0.5a with exactly the same behavior. The miss...

Does anyone have Samba working on Solaris 2.5.1? I posted more or less the same question a few months ago, and didn't hear anything back, but the issue has reared its head again on my end. I have Samba 2.0.0 running successfully on Solaris 2.6, but have failed in repeated attempts to get Samba running on Solaris 2.5.1. Basic symptom: I can get the daemon running, but can't connect to

...get a entry in the <machine name>.log that looks like: mircea:/usr/local/samba/var# cat log.mircea [1999/05/02 18:27:04, 0] locking/shmem.c:smb_shm_unregister_process(435) ERROR smb_shm_unregister_process : processreg_file open failed with code Permi ssion denied /usr/local/samba/var/locks/SHARE_MEM_FILE.processes ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ This is my contribution, I added in the debuging section of shmem.c the printing information for file name. On my system this file is created automatically when first message arrive and its permissions are 644 root:root. If some of you...

...get a entry in the <machine name>.log that looks like: mircea:/usr/local/samba/var# cat log.mircea [1999/05/02 18:27:04, 0] locking/shmem.c:smb_shm_unregister_process(435) ERROR smb_shm_unregister_process : processreg_file open failed with code Permi ssion denied /usr/local/samba/var/locks/SHARE_MEM_FILE.processes ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ This is my contribution, I added in the debuging section of shmem.c the printing information for file name. On my system this file is created automatically when first message arrive and its permissions are 644...

...__________________ WARNING smb_shm_open : filsize (0) !=expected size (1048576), using filesize ERROR smb_shm_vaildate_header : shmem not mapped ERROR smb_shm_open : corrupt shared mem file, remove it manually ERROR smb_shm_unregister : couldn't find pid 11530 in file /usr/local/samba/var/locks/SHARE_MEM_FILE.processes ERROR; Failed to initialise share modes! Can't initalise shared memory exiting Way over my head... any clue for the gurus out there? Thanks, Jason Pickering

...nect. Brian Lee Bowers | Division of Government Research Computer Aide III | University of New Mexico dgr0bb@unm.edu | ==================== log.smb ==================== [1999/05/27 13:07:03, 5] locking/shmem.c:smb_shm_open(819) smb_shm_open : using shmem file /usr/local/samba/var/locks/SHARE_MEM_FILE to be of size 1048576 [1999/05/27 13:07:03, 5] locking/shmem.c:smb_shm_register_process(402) smb_shm_register_process : writing record for pid 14897 at offset 0 [1999/05/27 13:07:03, 5] locking/shmem.c:smb_shm_initialize(525) smb_shm_initialize : initializing shmem file of size 1048576 [1999/05...

...=35 smb_com=0x73 smb_rcls=2 smb_reh=0 smb_err=2 smb_flg=128 smb_flg2=1 smb_tid=0 smb_pid=6237 smb_uid=1 smb_mid=41347 smt_wct=0 smb_bcc=0 end of file from client Closing connections smb_shm_close fcntl_lock 4 9 0 1 3 Lock call successful calling smb_shm_unregister_process(/usr/local/samba/var/locks/SHARE_MEM_FILE.process es, 18058) smb_shm_unregister_process : read record for pid 18058 smb_shm_unregister_process : erasing record for pid 18058 (seek_val = -4) fcntl_lock 4 9 0 1 2 Lock call successful 12/17/97 19:39:59 Server exit (normal exit) So I really don't know what to do now:-( P.S.: Thanks in...

...0 00 00 00 00 00 00 2B 00 ........ ........ [020] 00 00 8F 00 00 00 00 ....... write_socket(5,39) wrote 39 end of file from client Closing connections smb_shm_close fcntl_lock 4 7 0 1 2 Lock call successful calling smb_shm_unregister_process(/usr/local/samba/var/locks/SHARE_MEM_FILE.processes, 671088662) smb_shm_unregister_process : read record for pid 671088662 smb_shm_unregister_process : erasing record for pid 671088662 (seek_val = -4) fcntl_lock 4 7 0 1 3 Lock call successful 03/22/1999 07:30:04 Server exit (normal exit) SAMBA Server log 03/22/1999 07:30:00 client star...

...out_processing(854) end of file from client [2000/01/09 11:38:50, 2] smbd/server.c:exit_server(408) Closing connections [2000/01/09 11:38:50, 0] locking/shmem.c:smb_shm_unregister_process(475) ERROR smb_shm_unregister_process : couldn't find pid 1953 in file /usr/local/samba/var/locks/SHARE_MEM_FILE.processes [2000/01/09 11:38:50, 3] smbd/server.c:exit_server(435) Server exit (normal exit) Here is the output from testparm smb.conf: # testparm smb.conf Load smb config files from smb.conf doing parameter syslog = 3 doing parameter log file = /var/adm/smblogs/smblog Processing section &quo...

Hi! I've been struggling with this install of Samba 2.0.4b on Linux/x86 2.0.36. All of the client machines run Windows NT 4, SP 3. I'm exporting /tmp as pub, and if I right click in the folder and create a new folder, it doesn't show up until I go to 'view' and 'refresh'. If I delete something, it doesn't go away until I refresh. Why? Output of testparm: