| Title: | PATHWORKS for OSF/1 |
| Notice: | see also NOTED::PWDOSWINV5 (PW client) & TURRIS::DIGITAL_UNIX |
| Moderator: | CPEEDY::LONG |
| Created: | Thu Apr 22 1993 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 1874 |
| Total number of notes: | 6870 |
I have a customer who isrunning pw 5.0F eco1. Everything has been working fine then he started getting high cpu utilization on the Client process when a client prints. The server is fine with any other file operation, but when the client prints the process sends the CPU up to 90% or more. He has plenty of Swap space available, plenty of disk space and memory. We turned on DEBUG on the client lmx process then did a print and captured the following. puterror.c 148 16:46:16 smbwork: puterror (0, 0) smbwork.c 639 16:46:17 smbowkr NAFC!@ --SMB--> ioctl puterror.c 148 16:46:17 smbwork: puterror (1, 32) smbwork.c 639 16:46:17 smbwork: NAFC12 --SMB--> net use and X smbwork.c 639 16:46:17 smbwork: NAFC!@ --SMB --> transaction puterror.c 148 16:46:17 smbwork: puterror (2, 1) we stopped the debug after 5 minutes waiting for the print to come out, it takes the print job 20 minutes to complete a small job that use to be instant. I have had him check the rights on the lpr, since I saw this helped one user, that had mistakenly changed rights on some files but this did not help any ideas. the customer has reinstalled the product and is still having problems, he has recreated his pw queues that did not help. We have sent him 5.0g but this worked fine with the old version until now. I have not been able to proved he has changed anything. Help!! Andrea
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1767.1 | infos | NETRIX::"castello@mosupc.evt.DEC.COM" | UNIX-NT Gateway | Tue Mar 04 1997 16:10 | 29 |
Hi Andrea, some more information can help us (hope you too). 1/ Do you have the same pb from any PCs ? (WIN95, WFW,...) 1a/ What are the protocols used either by server and PCs ? It seems regarding your trace that the PC name is corrupted. and # puterror 1 32 Unsupported Utility.SMB error display.(DEC) JPC ERRDOS: ERRbadshare: The sharing mode specified for an Open conflicts with existing FIDs on the file. 2/ could you provide a complet trace log ? (and put it on the net location) Modify the lanman.ini just the time of tests. maxvcperproc =1 minvcperproc =1 In this case only one lmx.srv will serve one PC requests and the trace is much more useful. 3/ set sysqueuename=none in lanman.ini gives better performance on print subsystem. Regards, Jean-Pierre [Posted by WWW Notes gateway] | |||||