General

Re: samba cups printing difficulty

 
Stuart Browne
Honored Contributor

Re: samba cups printing difficulty

>>I would assume that sending a job from the command line would fail as well if this was a core directory.

>So far all the print job i gave are from command line using lp command.

What lp command are you using?

>>All samba is doing is launching a print-job command-line when one comes in, the same as if you typed 'lp -d '.
>>Have you tried doing the standard 'lp' comamnd and looking at the logs to see if a normal job works/fails/spits out errors?

>I am sorry. I dont understand what you mean by standard lp command. Please be more specific.

The command you used above.
One long-haired git at your service...
roopa
Occasional Advisor

Re: samba cups printing difficulty

What lp command are you using?

At first i was using....
lp -d %p -o filename

When you said about oraw i used...
lp -d %p -oraw filename.

If you look at the error log i pasted in my previous post, you will see that the process has been stopped with status 22. What does this status 22 mean.
Is there any way to find about this status 22? This might probably be a reason.

Thanks
Velu.
Stuart Browne
Honored Contributor

Re: samba cups printing difficulty

I don't know what status 22 is.. but change your reference to 'filename' to '%s', i.e.

print command = lp -d %p -oraw %s
One long-haired git at your service...
Mark Grant
Honored Contributor

Re: samba cups printing difficulty

Hi,

You might get more information if you change the debug level for cupsd. On Slackware it is /etc/cups/cupsd.conf but your mileage may vary. You can edit the "LogLevel" from the default of logging just requests and state changes to logging absolutely everything.

This may get more information that would be useful
Never preceed any demonstration with anything more predictive than "watch this"
Ross Carver
New Member

Re: samba cups printing difficulty


I hope this helps, but instead of having the "/etc/printcap" destination in the smb.conf, change it simply to "cups". Also,
go into the /etc/cups directory and edit the mime.* files.

Uncomment the commented lines at the end of each of these files which look like this:

application/octet-stream

This will substitute more consistently for the
print-command line in your smb.conf file.

Try that.

Oh, and you say you can't even execute the following command:

cat /etc/hosts | lpr ???

If this doesn't help, try the samba documentation...its long but its really good.

http://www.samba.org

~Ross