[Samba] Re: Printer Queue not being cleared

Rory Vieira rory.vieira at gmail.com
Tue Mar 14 15:19:27 GMT 2006


Dear Michael,

2006/3/14, Michael Lueck <mlueck at lueckdatasystems.com>:
>
> The rest looks "good" so I will focus two points on this part.
>
> > [printers]
> >    comment = All Printers
> >    path = /var/spool/samba
> >    browseable = no
> >    public = yes
> >    guest ok = yes
> >    writable = no
> >    printable = yes
> >    create mode = 0700
>
>    create mode = 0600
>
> Is perfect for this, spooled print jobs would never need to be executed on
> the server.
>
> Did you do something like this while setting up the spool directory? (Run
> as root)
>
> ==========================
> #!/bin/bash
> #
> # initPrint.sh
> #
>
> mkdir /var/spool/samba
> chmod 0777 /var/spool/samba
> chmod o+t /var/spool/samba
> ==========================


Yeah I did. On SuSE this folder doesn't exist by default, so my logs are
obviously cramped with statements that this folder doesn't exist. After
chmod 777 it also stop nagging about not being able to write LOL
Not sure what the chmod o+t means though...

Finally, have you looked in that directory to see if jobs are stuck there?


Well, that's my problem... There's nothing there. It's completely empty ?!?

"writable = no" strikes me as interesting... here is my printers share...
>
> [printers]
>    comment = SMB Print Spool
>    path = /var/spool/samba
>    browseable = no
>    public = yes
>    guest ok = yes
>    read only = yes
>    printable = yes
>    create mode = 0600
>
> Yes yes, small details, maybe one of them is key though...


I'll try this one out. Hopes that might fix some problems...
Idiotic thing is that using SuSE's default samba (3.0.13) doesn't have this
specific problem. It all started after upgading to 3.0.20b (before that we
were using 3.0.20a with no problems).
Cheers,
--
Rory Vieira
rory dot vieira at gmail dot com


More information about the samba mailing list