On Mon, Oct 27, 2014 at 11:38:29AM +0000, Brian Potkin wrote: > On Sun 26 Oct 2014 at 21:43:52 +0000, ael wrote: > > > Meanwhile I am attempting to capture the raw data sent to the printer as > > described in https://wiki.ubuntu.com/DebuggingPrintingProblems. However > > I am having trouble getting the output into a file. > > > > lpadmin -p test -v file:/tmp/printout ... > > > > does not seem to create the /tmp/printout. I tried -v > > file:///tmp/printout after consulting the lpadmin man page. > > > > The print jobs succeed, but no such file is created and so far I can't > > find where the output has gone... > > Under systemd a directory is created in /tmp. From memory it is has > 'cups' in its name. The file should be there. Get to it quickly because > I think it is deleted after x seconds.
Thanks for that. I am strongly tempted to swear given how much trouble systemd has caused me breaking all my debian testing boxes and frequently taking minutes to boot and to shutdown. Far longer than the old init system :-( One reason it has taken me so long to get around to looking for this cups bug was because I had to sort out systemd problems on several boxes. Sorry. This is off topic. I did look at /tmp/ immediately after the print jobs, and I would have noticed a cups directory, I think. But you have given me a clue. I hope to have time to have a look again later today. I did do a " find / -name printout" which I would have thought have found it even if somewhere systemd had tried to hide it... But maybe systemd had removed it by then in order to cause the maximum confusion. ael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
