[SLE] Samba, Cups and /etc/printcap

From: Hermann Gottschalk (hg_at_ostc.de)
Date: 07/30/04

  • Next message: Mike McMullin: "Re: [SLE] Think I've been cracked... not certain" 
    Date: Fri, 30 Jul 2004 11:15:59 +0200
To: suse-linux-e@suse.com

    Hi,
    following situation:

    1) You create a raw printer (called "testprinter") under cups and
    leave the description-field (info-field) empty. cups will create an
    entry in /etc/printcap of the form

    testprinter|testprinter:rm=linux100:rp=testprinter:

    2) You start samba with a standard [printers] and [print$] share.
    samba will expose the printqueue to the clients.

    3) You upload a windows printer driver via the Printer Wizard.
    This succeeds; the driver is uploaded.

    4) You try to install on an Windows-Workstation the printer and get
    the message, that there is no driver available.

    The reason is, that in ntdrivers.tdb the entry for the driver
    corresponding to the printqueue is missing.

    If you give the printqueue a description in the /etc/printcap (or
    under cups), no matter what kind of, all works fine.

    This seems to me, as if there is an unsufficient parsing of the
    /etc/printcap, because all information needed is in, even when
    queuename and description are equal (like in 1))

    System: SuSE 9.1 (2.6.5-7.95-default) Samba (3.0.2a-51)
    cups (1.1.20-103)

    Does anyone has the same problem?!

    Greetings Hermann 

    -- 
  ___  ___ _____ ___    ___       _    _  _
 / _ \/ __|_   _/ __|  / __|_ __ | |__| || |
| (_) \__ \ | || (__  | (_ | '  \| '_ \ __ |
 \___/|___/ |_| \___|  \___|_|_|_|_.__/_||_|
----------------------------------------------
 OSTC Open Source Training and Consulting GmbH
 Hermann Gottschalk  eMail:         hg@ostc.de
 90425 Nürnberg      Web:   http://www.ostc.de
----------------------------------------------
            PGP-Key: 0x0B2D8EEA 
    No HTML-Mails; 72 Characters per line

    • application/pgp-signature attachment: stored
  • Next message: Mike McMullin: "Re: [SLE] Think I've been cracked... not certain"

    Relevant Pages

    • Re: CTA - truck crash
      ... The driver in this accident has most certainly been cut loose and is now ... every entry you make in a logbook, when verifed, in order for that entry ... It's a game you can lose without even moving your ...
      (misc.transport.trucking)
    • Re: Loomis or Gordan?
      ... >> way to measure a driver, ... >> Main Entry: prog7nos7ti7ca7tion ... >> I know you want your prognostication to be fact. ... >> Perhaps I should also include OPINION: ...
      (rec.autos.sport.nascar)
    • RE: DBD::Solid or DBD::ODBC with Solid
      ... used by unixODBC and the shared object for your ... driver can be loaded then it should work. ... Entry: ... SQLState = ffbef4f0 ...
      (perl.dbi.users)
    • Re: Stream Device Driver
      ... you should not put your reg entry in ... the first prm of ActivateDeviceEx is not the path of your ... driver, but the registry base key that contain your driver's settings. ... with Dumpbin /exports mydriver.dll I see every entry point. ...
      (microsoft.public.windowsce.platbuilder)