Slashdot Mirror

← Back to Stories (view on slashdot.org)

Windows 2000, Samba, and Cancelling Print Jobs?

Posted by Cliff on from the I-said-WHOA-there-horsey! dept.

Kerry McDonald asks: "I have a Linux server running Samba, and my Windows 2000 users are unable to cancel print jobs once they are sent to the server. Has anyone seen this problem? I have checked all the Samba settings, and they all seem to allow user access, but for some reason it still will not work. Help!"

2 of 21 comments (clear)

  1. Linux print spooler by MrResistor · · Score: 5, Informative

    Probably it's just that samba doesn't have control of the Linux print spooler, so once the document is passed to the spooler you would have to cancel the job from Linux.

    It seems a little odd to me, that seems like something that would be fairly simple to set up, at least from the *nix end. There's the matter of trapping the correct command from the Windows side, of course, but that seems like one they would have caught by now. Is the problem just under Windows 2000, or other Windows versions as well?

    --
    Under capitalism man exploits man. Under communism it's the other way around.
  2. Printing.txt in the docs... by Anonymous Coward · · Score: 5, Informative

    And I quote:

    The following are nice to know about:

    queuepause command - stop a printer or print queue
    queueresume command - start a printer or print queue

    Example:
    print command = /usr/bin/lpr -r -P%p %s
    lpq command = /usr/bin/lpq -P%p %s
    lprm command = /usr/bin/lprm -P%p %j
    queuepause command = /usr/sbin/lpc -P%p stop
    queueresume command = /usr/sbin/lpc -P%p start

    Samba should set reasonable defaults for these depending on your
    system type, but it isn't clairvoyant. It is not uncommon that you
    have to tweak these for local conditions. The commands should
    always have fully specified pathnames, as the smdb may not have
    the correct PATH values.
    You DID check those, right?