Does anyone know of a way to maintain the Windows print job name with samba on a print job? i.e. NOT smbprn_0000126_InbAMi but Security HOW-TO... Thanks ahead of time... Wade Winright "Open the pod bay doors HAL!!!" -Arthur C. Clarke -------------- next part -------------- HTML attachment scrubbed and removed
This question has been asked and ignored before, so it sounds like a long shoot. It SEEMS like this should be doable but I don't see where the name of the windows file is passed to samba. I just tried a few things: I made max jobs = 1. I was hoping that windows would just keep the job in the windows queue with its windows name, but it refused to print it. I disabled spooling on windows, printing directly to the printer. That didn't help either. Of course, the print jobs have to have unique names, so the name of the windows file can't be the name which is tracked in the spooler. The solution might be to get windows not to send a print job to the server unless the printer is free, but I don't see any spooler adjustment for that and then of course your job might never get printed. The only thing I could find was to take the printer on windows off line. Then, the jobs stay on windows with their own file names, but, they are not being printed during this time. I suspect the root problem is that windows won't pass the file name to samba. This is the sort of thing that a linux person would solve with a script but I do not know anything about windows scripting, nor if such a thing even exists. Joel> Does anyone know of a way to maintain the Windows print job name with samba > on a print job? i.e. NOT smbprn_0000126_InbAMi but Security HOW-TO... > Thanks ahead of time... > > Wade Winright > "Open the pod bay doors HAL!!!" > -Arthur C. Clarke >
Hi,> I'm the one who posted the message to the other thread that suggested adding > the -J'%J' to the print command setting in smb.conf. FYI, I picked this from > someone else on this list several months ago. > > I just tested to see if my print job names were being similarly truncated > and they are not. I specifically tested printing from MS Word and all was > OK. > > For comparison, I'm running Samba 2.2.1a+LDAP patch on RedHat 7.1. The > client I test-printed from is Win2K Pro SP 2. The printer (not that it > should matter) is an HP 5Si. Obviously, I'm using LPRng (3.7.4-22 from RPM). > > Can you determine if names are being truncated consistently to a specific > length? Does printing from all clients/different client OS exhibit the same > behavior? (Grasping at straws here)I experience the truncating too. But I think the problem is lying in the underlying printing subsystem. Just look: odenbach@robin[~]>>echo bla | lpr -J'1234567890123456789012345678901234567890' This print job name has a length of 40 characters. odenbach@robin[~]>>lpq Printer: lw_sw_rbg_1_F0_113@pooh (dest lw_sw_rbg_1_F0_113@pooh) 'HP LaserJet 5MP in F0.113' (printing disabled) Queue: 1 printable job Server: no server active Status: server finished at 12:29:34 Rank Owner/ID Class Job Files Size Time 1 odenbach@robin+184 A 184 12345678901234567890123 4 08:48:01 lpq just gives me the first 23 characters of the job name. This is also the number of characters that are visible in windows - which is not very surprising as Samba just parses the output of lpq. So the interesting question is: How does the output of lpq look like with a system that does not truncate the job name? Regards, Christopher