search for: rolandhordo

Hi, I believe that the BUG 2346 which was resolved in samba 3.0.14 has come back in the 3.0.23 series. Here is what I have noticed on two separate configurations. The samba packages were built on each machine using rpmbuild with the SRPMS provided for Fedora in the samba web site. Configuration 1. Two machines running with RHEL4, samba 3.0.23b-1, drbd-0.7.21 protocol C. Kernel:

Hi, I've posted the same problem several months ago, You can find my post there: http://lists.samba.org/archive/samba/2006-March/119244.html I summed up all the whole thing: I run a samba server based on slackware 10.2, using samba 3.0.20 with two clients: a windows 98 box and a windows 2000 box. I've got a share between the two system which hosts an old spreadsheet program (quattro pro)

I'm trying to join my FC6 box to our Active Directory domain. For the most part the setup was pretty straightforward, but it just doesn't seem like winbind separator is being honored. When I do a 'getent passwd' I get the following: AVWORLD\johnXXXX:*:16782801:16777216:XXXXXXXX:/home/AVWORLD/johnXXXX:/bin/bash

Hi, When using lsof, I see that smbd changes ownership from the actual user who made the connection, to root. Also seeing odd behavior with certain files accessed from XP boxes suddenly becoming "read only" to the user mid edit, and appears to be related. Ex: lsof output at 8:45 AM: smbd 11987 user1 cwd DIR 253,3 4096 704687 /home/Shares/Groups within a

Hi, We have a problem like I've never seen in 8 years of running Samba in production. Two users can overwrite each other's open Excel spreadsheets. It occurs very infrequently, basically randomly, never happens on a recently restarted smbd instance, and is extremely difficult to troubleshoot due to samba switching process ownership from the user to "root" shortly after

Hi, It would be very useful to have a parameter(s) that allows a list of IP addresses, for which verbose debugging takes place. This would be extremely helpful for tracking odd cases that do not occur consistently, and for troubleshooting machine-specific issues. example smb.conf entries: debug ip list level = 10 debug ip list = 192.168.0.151 192.168.0.136 Ideally this would be available