It seems like the files sent to the samba spool and then over to CUPS seem to stay in the /var/spool/samba directory indefinately. Is there a fix to this via a configuration, or just setting up a cron job to purge? Thanks
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 22 May 2003, Chris McKeever wrote:> It seems like the files sent to the samba spool and then over to CUPS seem > to stay in the /var/spool/samba directory indefinately. > > Is there a fix to this via a configuration, or just setting up a cron > job to purge?This was fixed in some of the more recent 2.2 release. sounds like you have an old installation. cheers, jerry ---------------------------------------------------------------------- Hewlett-Packard ------------------------- http://www.hp.com SAMBA Team ---------------------- http://www.samba.org GnuPG Key ---- http://www.plainjoe.org/gpg_public.asc "You can never go home again, Oatman, but I guess you can shop there." --John Cusack - "Grosse Point Blank" (1997) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQE+zkk1IR7qMdg1EfYRAgwiAKDCumApaQeXhlS7OY193xgW6ON5WACg7QH+ PUjfvr4xLVPryReOdRvGklM=BRZ1 -----END PGP SIGNATURE-----
man, I thought the list was dead! anyway, I am running 2.2.8m but I ofund that I needed to add ;rm %s to my print command! Thanks> -----Original Message----- > From: Gerald (Jerry) Carter [mailto:jerry@samba.org] > Sent: Friday, May 23, 2003 11:16 AM > To: Chris McKeever > Cc: 'Uwe Laverenz'; samba@lists.samba.org > Subject: Re: [Samba] /var/spool/samba retention period > > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Thu, 22 May 2003, Chris McKeever wrote: > > > It seems like the files sent to the samba spool and then > over to CUPS seem > > to stay in the /var/spool/samba directory indefinately. > > > > Is there a fix to this via a configuration, or just setting > up a cron > > job to purge? > > This was fixed in some of the more recent 2.2 release. > sounds like you > have an old installation. > > > > > cheers, jerry > > ---------------------------------------------------------------------- > Hewlett-Packard -------------------------http://www.hp.com SAMBA Team ---------------------- http://www.samba.org GnuPG Key ---- http://www.plainjoe.org/gpg_public.asc "You can never go home again, Oatman, but I guess you can shop there." --John Cusack - "Grosse Point Blank" (1997) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQE+zkk1IR7qMdg1EfYRAgwiAKDCumApaQeXhlS7OY193xgW6ON5WACg7QH+ PUjfvr4xLVPryReOdRvGklM=BRZ1 -----END PGP SIGNATURE-----
> > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Fri, 23 May 2003, _Chris McKeever_ wrote: > > > man, I thought the list was dead! > > > > anyway, I am running 2.2.8m but I ofund that I needed to add > > ;rm %s > > to my print command! > > If you have 'printing = cups' and smbd is linked with > the CUPS libs, then you shouldn't need a print command at all. > Other wise, yes you will need to remove the file as part of > the print command. > >This is how I have it set up, but I dont know what you mean by smbd is linked with the CUPS libs, here is a snippet of my smb.conf (I defined them individually because of permissions on some): [konica-3rd] printer = konica_3rd printing = cups comment = Konica 7135 - 1201 3rd Floor path = /var/spool/samba browseable = yes guest ok = yes writable = no printable = yes print command = lpr.cups -P %p -o raw %s;rm %s lpq command = lpstat.cups -o %p lprm command = cancel.cups %p-%j> > > > cheers, jerry > > ---------------------------------------------------------------------- > Hewlett-Packard -------------------------http://www.hp.com SAMBA Team ---------------------- http://www.samba.org GnuPG Key ---- http://www.plainjoe.org/gpg_public.asc "You can never go home again, Oatman, but I guess you can shop there." --John Cusack - "Grosse Point Blank" (1997) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQE+zk+7IR7qMdg1EfYRAke1AJwKM3O4R4mfeNpS3iTiflHrChbfUwCePM8F BtQjfdzvJYAqOAk6iJowHaw=sYW0 -----END PGP SIGNATURE-----
> > > anyway, I am running 2.2.8m but I ofund that I needed to add > > ;rm %s > > to my print command! > > You are trying to solve a CUPS problem using Samba. Suggest > you check your > /etc/cups/cupsd.conf file. There is an option there to delete spent > entries. The old ones hang around to allow any job to be reprinted. > > Check what is the setting of "AutoPurgeJobs", you might be > surprised how > helpful that option can be. :) >I have the cups portion working using the "Maxjobs" config in the cups.conf..it was just doubling up the files by keeping one set in /var/spool/samba after it send it to the cups spool...> - John T. > > > > > Thanks > > > > > > > -----Original Message----- > > > From: Gerald (Jerry) Carter [mailto:jerry@samba.org] > > > Sent: Friday, May 23, 2003 11:16 AM > > > To: Chris McKeever > > > Cc: 'Uwe Laverenz'; samba@lists.samba.org > > > Subject: Re: [Samba] /var/spool/samba retention period > > > > > > > > > -----BEGIN PGP SIGNED MESSAGE----- > > > Hash: SHA1 > > > > > > On Thu, 22 May 2003, Chris McKeever wrote: > > > > > > > It seems like the files sent to the samba spool and then > > > over to CUPS seem > > > > to stay in the /var/spool/samba directory indefinately. > > > > > > > > Is there a fix to this via a configuration, or just setting > > > up a cron > > > > job to purge? > > > > > > This was fixed in some of the more recent 2.2 release. > > > sounds like you > > > have an old installation. > > > > > > > > > > > > > > > cheers, jerry > > > > > > > ---------------------------------------------------------------------- > > > Hewlett-Packard ------------------------- > > http://www.hp.com > > SAMBA Team ----------------------http://www.samba.org> GnuPG Key ---- http://www.plainjoe.org/gpg_public.asc > "You can never go home again, Oatman, but I guess you can shop there." > --John Cusack - "Grosse Point Blank" (1997) > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.0 (GNU/Linux) > Comment: For info see http://quantumlab.net/pine_privacy_guard/ > > iD8DBQE+zkk1IR7qMdg1EfYRAgwiAKDCumApaQeXhlS7OY193xgW6ON5WACg7QH+ > PUjfvr4xLVPryReOdRvGklM> =BRZ1 > -----END PGP SIGNATURE----- >-- John H Terpstra Email: jht@samba.org
John H Terpstra jht at samba.org Hi, Jan!> Fri May 23 20:30:27 GMT 2003 > > > On Fri, 23 May 2003, _Chris McKeever_ wrote: > >> man, I thought the list was dead!I wondered too where Chris acquired the boldness to exclamate such a claim. He must be knowing some other lists, where an answer to any question is forthcoming within less than 20 hours.> No, the list is not dead. It's just that it would take two people full > time to keep up with requests to this list and we have incredible > difficulty making any team member work on the list given the exceptional > pay provided! >Quite right, Jan!>> anyway, I am running 2.2.8mThis version is unknown to me. Where might he have gotten it, Jan?>> but I ofund that I needed to add >> ;rm %s >> to my print command! > > You are trying to solve a CUPS problem using Samba.Not quite right here, Jan. The complaining party pointed at files remaining in "/var/spool/samba/" (the recommended Samba spool dir), not the ones in "/var/spool/cups/". Since the complainant didn't bother to give a commonly known version number for Samba or CUPS it is extremely difficult for anyone of our voluntary support staff to come up with any remedy (especially since most of our in-house crystal balls are broken since a long time...) within our standard timeframe for free-of-charge world class special support. However, he might have stumbled over a real bug which was present in one older 2.2.x version. But we don't know for sure... We don't even know his current configuration settings in smb.conf. But he asks to get advice to change his configuration. Do you think it is a fair verdict, Jan, if we point him to the documents like http://www.cups.org/cups-help.html or http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/ and ask him to try an help himself in record-time?> Suggest you check your > /etc/cups/cupsd.conf file. There is an option there to delete spent > entries. The old ones hang around to allow any job to be reprinted.These ones would hang around in "/var/spool/cups/"> Check what is the setting of "AutoPurgeJobs", you might be surprised how > helpful that option can be. :) > > - John T.Cheers, Kurt
> > On Fri, 23 May 2003, _Chris McKeever_ wrote: > > > >> man, I thought the list was dead! > > I wondered too where Chris acquired the boldness to exclamate > such a claim. > > He must be knowing some other lists, where an answer to any > question is > forthcoming within less than 20 hours.No..I meant it from the standpoint that the day I posted, I didnt recieve ANY messages from the entire list (not intending to mean responses to my issue)..and my posts didnt get delived to me till the next day..I meant it as list server was dead, not the reponse mechanism was dead..2D sarcasm is tough to view I guess> > > No, the list is not dead. It's just that it would take two > people full > > time to keep up with requests to this list and we have incredible > > difficulty making any team member work on the list given > the exceptional > > pay provided! > > > > Quite right, Jan! > > >> anyway, I am running 2.2.8m > > This version is unknown to me. Where might he have gotten it, Jan? > > >> but I ofund that I needed to add > >> ;rm %s > >> to my print command! > > > > You are trying to solve a CUPS problem using Samba. > > Not quite right here, Jan. > > The complaining party pointed at files remaining in > "/var/spool/samba/" > (the recommended Samba spool dir), not the ones in "/var/spool/cups/". >I dont feel that I was complaining one bit ;) .. concerned of the list _server_ status> Since the complainant didn't bother to give a commonly known version > number for Samba or CUPS it is extremely difficult for anyone of our > voluntary support staff to come up with any remedy (especially since > most of our in-house crystal balls are broken since a long time...) > within our standard timeframe for free-of-charge world class special > support. > > However, he might have stumbled over a real bug which was present > in one older 2.2.x version. But we don't know for sure... > > We don't even know his current configuration settings in smb.conf. > But he asks to get advice to change his configuration. > > Do you think it is a fair verdict, Jan, if we point him to > the documents > like > > http://www.cups.org/cups-help.html > > or > > http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/ > > and ask him to try an help himself in record-time? > > > Suggest you check your > > /etc/cups/cupsd.conf file. There is an option there to delete spent > > entries. The old ones hang around to allow any job to be reprinted. > > These ones would hang around in "/var/spool/cups/" > > > Check what is the setting of "AutoPurgeJobs", you might be > surprised how > > helpful that option can be. :) > > > > - John T. > > Cheers, > Kurt > > -- > To unsubscribe from this list go to the following URL and read the > instructions: http://lists.samba.org/mailman/listinfo/samba >