From: jsie...@panix.com (Jonathan Siegel) Subject: Samba/SunOS/Win4WG Print Manager S L O W!! Date: 1996/01/30 Message-ID: <4elr1l$1dm@panix.com>#1/1 X-Deja-AN: 137220712 organization: Panix newsgroups: comp.protocols.smb Hi, Folks -- We're running samba under SunOS 4.1.3, connecting drives and printers to Win4WG clients. We had a few problems with initial compilation, but all now works as advertized, with the following exception: When Print Manager is opened on a Win4WG client with a UNIX printer connected via SAMBA, everything on the client goes into s l o w motion. It takes approximately 45 seconds to 1 minute before mouse events are recognized on the client, and approximately 45 seconds to update the print manager screen after connecting a UNIX printer. The printing itself works fine as long as Print Manager is not open. With it open, even minimized on the desktop, client systems are impossible to use. Anyone else experienced this? Any suggested fixes? We see no errors in the relevant log files, and our printer configuration in smb.conf is pretty much the "out-of-the-box" setup for bsd. Thanks in advance -- Jonathan Siegel
From: tri...@cs.anu.edu.au (Andrew Tridgell) Subject: Re: Samba/SunOS/Win4WG Print Manager S L O W!! Date: 1996/02/15 Message-ID: < vvlom5127b.fsf@cs.anu.edu.au>#1/1 X-Deja-AN: 139510493 sender: tri...@cs.anu.edu.au references: <4elr1l$1dm@panix.com> organization: ANU reply-to: Andrew.Tridg...@anu.edu.au newsgroups: comp.protocols.smb > When Print Manager is opened on a Win4WG client with a UNIX printer > connected via SAMBA, everything on the client goes into s l o w motion. > It takes approximately 45 seconds to 1 minute before mouse events are > recognized on the client, and approximately 45 seconds to update the > print manager screen after connecting a UNIX printer. The problem is that whenever a WfWg box asks for the printer status Samba has to execute a "lpq" to get it. While its waiting for the answer your WfWg box is frozen, due to the way multi-tasking is handled in windows. Your lpq must also be very slow. To combat this you can do a number of things: - in recent versions of Samba (at least 1.9.15) you can set the "lpq cache time" to a reasonable limit so all your PCs will share a cache of lpq results. This helps a lot. - work out why your lpq is so slow. How long does the command "lpq" take at the command line? Andrew -- -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Andrew Tridgell Dept. of Computer Science email: Andrew.Tridg...@anu.edu.au Australian National University Phone: (06) 254 8209 or (06) 249 5691 Fax: (06) 254 9673 or (06) 249 0010 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-