Le lundi 22 janvier 2007 11:58, Christian Pinedo Zamalloa a écrit : Ok, I read your 2 mails, and this seems to get better :-)
> Jan 22 11:45:28 bipt02 jasmine[52865]: Warning: Debug mode is activated, > you should turn it off when going to production ! To do so, set $Debug_Mode > to 0 in the /usr/local/libexec/cups/backend/jasmine perl script. [...] > Jan 22 11:45:28 bipt02 jasmine[52865]: - DEVICE_URI= > jasmine:lpd://bipt171.bi.ehu.es > Jan 22 11:45:28 bipt02 jasmine[52865]: - SOFTWARE= CUPS/1.2.7 > Jan 22 11:45:28 bipt02 jasmine[52865]: - TMPDIR= /var/spool/cups/tmp > Jan 22 11:45:28 bipt02 jasmine[52865]: - > CUPS_SERVERROOT= /usr/local/etc/cups Well, something's wrong : The log really stops here ? This means that the print job is not successfully sent to the real backend, or that it actually is, but te real backend cannot contact te printer. Ok, it's now time to fire our secret weapon : Dummy. It is the dummy printer backend, which prints nothing, but is great to debug jasmine. So, all you have to do is setup a new printer (in the http://cups_server:631 interface) using the dummy backend (in the dropdown list, choose "Really virtual printer for testing Cups (quota managed)") and give this URI : "jasmine:dummy:nothing". Next, print somethig to it : You should see in the logs whether the job was succesful or not. If it failed, then the issue is jasmine-related. I no, it means that you may have a problem with "bipt171.bi.ehu.es" : Network, syntax, etc... The device_uri for it seems good, jasmine-wise : "jasmine:lpd://bipt171.bi.ehu.es". So try to resolve the name, or ping it, etc. > I hope this to be more useful. Slowly but we are making progress. Thanks, Yes ;-) ! Sorry for being slow to answer on this, I had some server install this week ;-) -- Put JASmine in your Cups ! To unsubscribe : mailto:[EMAIL PROTECTED] List archives : http://dir.gmane.org/gmane.comp.printing.jasmine.user http://www.mail-archive.com/jasmine%40ml.free.fr/ Web site : http://jasmine.berlios.de/
