Hi Everybody, I seem to still be having problems with the caching of files on the PC. I have tried to set the oplocks = false variable in the smb.conf file but that has not seemed to help. Here is what I do to see the problem Open a file on the PC, the close it. Go to a unix machine and modify the file. Go back to the PC and re-open the file. I will get the old copy of the file for a few minutes. Eventually the new one will show up, but I dont want to have to wait. I am including the output of the testparm in case that will help. I also just noticed that when I decrease the file size the PC will only show my part of the original file. So if there were 50 characters originally but now there are only 10 characters I will see only 10 characters when I re-open the file, but it will be the first 10 characters of the old file, not the new one. (At least for a few minutes) Thanks for any help, or pointers, David. Load smb config files from /usr/local/samba/lib/smb.conf Processing section "[pc]" Loaded services file OK. Press enter to see a dump of your service definitions # Global parameters workgroup = WORKGROUP netbios name = netbios aliases = server string = Samba 2.0.0-beta1 interfaces = bind interfaces only = No security = USER encrypt passwords = No update encrypted = No use rhosts = No map to guest = Never null passwords = No password server = smb passwd file = /usr/local/samba/private/smbpasswd hosts equiv = root directory = / passwd program = /bin/passwd passwd chat = *old*password* %o\n *new*password* %n\n *new*password* %n\n *changed* passwd chat debug = No username map = /opt/samba/lib/umap password level = 0 username level = 0 unix password sync = No log level = 2 syslog = 1 syslog only = No log file = max log size = 5000 timestamp logs = Yes protocol = NT1 read bmpx = Yes read raw = Yes write raw = Yes nt smb support = Yes nt pipe support = Yes announce version = 4.2 announce as = NT max mux = 50 max xmit = 65535 name resolve order = lmhosts host wins bcast max packet = 65535 max ttl = 259200 max wins ttl = 518400 min wins ttl = 21600 time server = No change notify timeout = 60 deadtime = 0 getwd cache = Yes keepalive = 300 lpq cache time = 10 max disk size = 0 max open files = 10000 read prediction = No read size = 16384 shared mem size = 1048576 socket options = TCP_NODELAY stat cache size = 50 load printers = Yes printcap name = /etc/printcap printer driver file = /usr/local/samba/lib/printers.def strip dot = No character set = mangled stack = 50 coding system = client code page = 850 stat cache = Yes domain groups = domain admin group = domain guest group = domain admin users = domain guest users = machine password timeout = 604800 logon script = logon path = \\%N\%U\profile logon drive = logon home = \\%N\%U domain logons = No os level = 0 lm announce = Auto lm interval = 60 preferred master = No local master = Yes domain master = No browse list = Yes dns proxy = Yes wins proxy = No wins server = wins support = No kernel oplocks = Yes ole locking compatibility = Yes smbrun = /usr/local/samba/bin/smbrun config file = preload = lock dir = /opt/samba/lib/locks default service = message command = dfree command = valid chars = remote announce = remote browse sync = socket address = 0.0.0.0 homedir map = time offset = 0 unix realname = No NIS homedir = No panic action = comment = path = alternate permissions = No revalidate = No username = guest account = nobody invalid users = valid users = admin users = read list = write list = force user = force group = read only = Yes create mask = 0744 force create mode = 00 directory mask = 0755 force directory mode = 00 guest only = No guest ok = No only user = No hosts allow = hosts deny = status = Yes max connections = 0 min print space = 0 strict sync = No sync always = No print ok = No postscript = No printing = sysv print command = lp -c -d%p %s; rm %s lpq command = lpstat -o%p lprm command = cancel %p-%j lppause command = lp -i %p-%j -H hold lpresume command = lp -i %p-%j -H resume queuepause command = lpc stop %p queueresume command = lpc start %p printer name = printer driver = NULL printer driver location = default case = lower case sensitive = No preserve case = Yes short preserve case = Yes mangle case = No mangling char = ~ hide dot files = Yes delete veto files = No veto files = hide files = veto oplock files = map system = No map hidden = No map archive = Yes mangled names = Yes mangled map = browseable = Yes blocking locks = Yes fake oplocks = No locking = Yes oplocks = Yes strict locking = Yes share modes = Yes copy = include = exec = postexec = root preexec = root postexec = available = Yes volume = fstype = NTFS set directory = No wide links = Yes follow symlinks = Yes dont descend = magic script = magic output = delete readonly = No dos filetimes = No dos filetime resolution = No fake directory create times = No [pc] path = /NEWPC read only = No guest only = Yes guest ok = Yes oplocks = No
Many Thanks in Advance:
OS Solaris 2.5.1
Samba 1.9.16 p1
We are running a few networks with C subnets that have between 20 and 200
clients(win95) on each. Everything on the file side is golden, however
printing is another story.
If a PC on the net prints a job, the job is moved to the printer without
any issues. (The printers are HP's with Jetdirect cards) However, when
another (or the same) PC prints a second job -while- the first job is still
being moved from the server to the printer, all applications on the second
jobs PC freeze. Tracing the network shows that there is no information
coming BACK from SAMBA, however, the PC is looking(requesting) information
on the printing port of the SAMBA server. Clear?? Clear as mud? ;}
My WAG is that the PC is expecting status information from the LANMANGER
(samba) server as to the print job status, and blocks application operation
while trying to update the printer status.
Now my questions:
1. Is there an authoritive method for setting up printing in SysV
environment or BSD environment?
2. Has anyone noted this 'feature' before?
3. Any ideas as to fixes/work arounds?
Relevant smb.conf here
---------------------------
[global]
; printing = bsd
workgroup = GaleMA
server string = Gale Server
debug level = 2
printcap name = lpstat
load printers = yes
[printers]
comment = All Printers
path = /usr/spool/samba
browseable = no
printable = yes
public = no
writable = no
create mode = 0700
[civ-las]
browseable = yes
Comment = Down stairs LaserJet 4
printer = civ-las
path = /tmp
guest ok = yes
read only = no
print ok = yes
If you use NT4 with SP3, The NT box does not permit using "plaintext passwords", the solution is either making NT accept using "plaintext passwords", this is descriped in the doc file "WinNT.txt", or configure samba to use encrypted passwords, this is descriped in the doc file "ENCRYPTION.txt" echo '16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlbxq'|dc> > Date: Mon, 16 Nov 1998 11:02:55 +0100 > From: "Jean-Francois COUTEL" <coutel@initiative.fr> > To: <samba@samba-ntdom.anu.edu.au>, <samba@samba.anu.edu.au> > Subject: password error from NT4 to redhat 5.1 samba server > Message-ID: <000601be1148$47f4dde0$2601030a@maranello.initiative.fr> > > I have a samba server 1.9.18 in linux redhat 5.1 > I use WinNt4 to see directory in the linux host. > > in windows nt, the command "net view" show > > "\\tahiti" > > the command "net view \\tahiti" show > > " l'erreur systeme 86 a eu lieu > le mot de passe reseau sp?cifi? est incorrect" > > What is the solution? > > COUTEL Jean-Francois > 01 40 90 30 50 > coutel@initiative.fr >-- Regards Per \|/ (o *) ---------------------------------------------------oOOO--(_)- | Per Kofod / Systems Engineer Email: per@copen.sgi.com | | Silicon Graphics Denmark Fax: (+45) 43270481 O | Stationsparken 25 Phone: (+45) 43438600 O | 2600 Glostrup VNET 540-0431 O | DENMARK URL: http://www.sgi.dk o ------------------------------------------------------------- *** People not living on the edge, takes up too much space. ***
Apparently Analagous Threads
- password error from NT4 to redhat 5.1 samba server
- Why does oplocks = False not seem to stop file cacheing? (More Info)
- (Correction) File caching while "oplocks=False", black magic or what?
- Problem w/ Belkin UPS on FreeBSD
- Why does oplocks = False not seem to stop file cacheing?