samba - Aug 2004 - printernames vs. sharenames

Hello,

when I assign a printer driver to a printer from a windows client, the 
printername now changes to the drivername.

Yes, I can see the SPOOLSS_SETPRINTER call with the printername property, 
but that's definitly not what I want (or would expect).

E.g. when I change the drivers of 3 printers to HP Laserjet, I get 3 printers 
with the names "HP Laserjet [(Copy 1|2)]". These names are different
from the
names of my CUPS queues and have to be reverted manually.

We all work with and configure the printers having the sharenames (aka the 
queue names) in mind. And -btw- it does not happen, when changing the printer 
driver of a local queue. 

Just my point of view... any comments?


P.S.
To the topic "print spooling messages never go away": 
We're not able to reproduce it with 3.06rc2. We'll still have an eye on
that
but can't provide reasonable infos now.

Bye,
Martin

-- 
Martin Zielinski ? ? ? ? ? ? ? ? ? ? ? mz@seh.de
Software Development
SEH Computertechnik GmbH ? ? www.seh.de

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Martin Zielinski wrote:
| Hello,
|
| when I assign a printer driver to a printer from a
| windows client, the  printername now changes
| to the drivername.
|
| Yes, I can see the SPOOLSS_SETPRINTER call with the
| printername property, but that's definitly not what I
| want (or would expect).

This is actually windows behavior.  As you mention, it
is the client spooler to the SetPrinter() call.  You
can see the same thing locally if the printername is
the previous driver name.

| E.g. when I change the drivers of 3 printers to HP Laserjet, I
| get 3 printers  with the names "HP Laserjet [(Copy 1|2)]". These
| names are different from the  names of my CUPS queues and have
| to be reverted manually.
|
| We all work with and configure the printers having the
| sharenames (aka the  queue names) in mind. And -btw- it does
| not happen, when changing the printer driver of a local
| queue.
|
| Just my point of view... any comments?

Changing a driver should happen in frequently I expect.
If people find the behavior worse than not being able to
change the printername at all, then we can set some method
of enforcing the printername == sharename model again.
Kind of late for 3.0.6 though.

| To the topic "print spooling messages never go away":
| We're not able to reproduce it with 3.06rc2. We'll still
| have an eye on that  but can't provide reasonable infos now.

ok.  Hopefully this is fixed.





cheers, jerry
- ---------------------------------------------------------------------
Alleviating the pain of Windows(tm)      ------- http://www.samba.org
GnuPG Key                ----- http://www.plainjoe.org/gpg_public.asc
"If we're adding to the noise, turn off this song"--Switchfoot
(2003)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFBJL3/IR7qMdg1EfYRAqTfAKC3OcWqDiM15STY2x4jV9N1dQZiQACgv90Y
U323MlSzED1oIRx0V23fNXo=ubKi
-----END PGP SIGNATURE-----