I tried your suggestion.
I did not disable logging, because I have found not entries in either the messages or secure log during these delay times. I did find these entries in /var/lob/samba/log.smbd:
[2009/11/04 13:35:52, 1] smbd/service.c:close_cnum(
192.168.101.63 (192.168.101.63) closed connection to service sysroot
[2009/11/04 13:35:53, 0] smbd/server.c:main(944)
smbd version 3.0.33-3.7.el5 started.
Copyright Andrew Tridgell and the Samba Team 1992-2008
[2009/11/04 13:36:33, 1] smbd/service.c:make_connec
192.168.101.61 (192.168.101.61) connect to service sysroot initially as user nobody (uid=99, gid=99) (pid 29840)
[2009/11/04 13:49:30, 1] smbd/service.c:close_cnum(
192.168.101.61 (192.168.101.61) closed connection to service sysroot
[2009/11/04 13:49:30, 0] smbd/server.c:main(944)
smbd version 3.0.33-3.7.el5 started.
Copyright Andrew Tridgell and the Samba Team 1992-2008
[2009/11/04 13:50:09, 1] auth/auth_util.c:create_to
lookup_name_smbconf for guest failed
After I made the changes you suggested (except the turning off logging, which I reserve for a last resort...)
I stopped Accurev and restarted it and I got an error popup that looked like the attached picture. Previously, I just had long delays after initial startup, the pop-up error is new. Once I click OK on the pop-up, things still work, but with the same long delay.
One thing that I have consistently had problems with is browsing to a Samba share by name.
If I want to look at a file on /etc/samba/ for instance, on a the Linux samba share 'sysroot' (see the code snippet, where I pasted my smb.conf file). I can do it two ways:
1. browse to workgroup Linux click on ASSETx and then to \sysroot\etc\samba\
OR
2. browse directly to \\192.168.101.65\sysroot\e
Method 1 ALWAYS takes a long time and often results in the browser pane getting hung up and having to be killed. I usually never even get to see the ASSETx object.
Method two (which is how I do it in Accurev) always works instantly and I've been using this samba conf file with minor variations on a dozen Linux boxes here every day for 4 years with no issues at all. Using this method, file copies, editor reads and writes, BeyondCompare, AraxisMerge, etc. ALL work flawlessly.
But with this one application, Accurev, I have these extremely long delays.
I am behind a really secure firewall, so I have all the Linux security disabled and always run as root. They are strictly engineering development platforms. I wrestled with Samba and Windows ADS for weeks until it made me insane, so I removed all the security s**t and opened the shares up to the public and since then, everything has run smoothly (until Accurev).
So I wonder if I should make all the files in my primary share owned by root and set up smb.conf share to force user = root, rather than guest?
I'm going to try that and see what happens.
Main Topics
Browse All Topics





by: it4sohoPosted on 2009-11-03 at 14:47:14ID: 25734733
It sounds to me like you're experiencing some type of a timeout, thus delaying access.
You said: "We do not have to enter passwords to access the shares"
But regardless, I'm guessing that Samba is trying at least one of these:
1) validating a user (the user you're logged in as on the client)
2) validating a host (which probably involves a reverse DNS lookup or a NetBIOS query)
In either case, the request for data is having to timeout before access is being granted.
Try the following:
A) force all access to the shares to be by "guest" user (there is a force user option for each share)
B) enter the line below to optimize socket utilization (goes in the GLOBAL section):
socket options = TCP_NODELAY SO_RCVBUF=16384 SO_SNDBUF=16384
C) as a last resort, disable logging (log level = 0)
Good Luck!
Dan
IT4SOHO