On Sun, 03 Aug 2003 12:19:21 +1200 Andrew Packer <[EMAIL PROTECTED]> wrote:
> Thank you for the tip re su -. Trying to sort out one problem I find > I learn all kinds of things applicable to other problems (now if I > could only remember some of them...). > i sometimes think i need a notebook! > The cups config files are identical on my machine (where it works > flawlessly) and hers (where it doesn't). > > I've managed to telnet to port 631 both locally and also from the > other PC on the network, but I don't know what to do after I get > connected. > all it shows at this point is that the port is open and reachable! > I've had a squiz at /var/log/cups/error_log. Much gibberish to me but > I do note this: I cat the error log, try to print something, cat the > error log again; the error log reads exactly the same before and after > the attempt to print. Logic suggests to me that the error is > occurring before the file-to-be-printed gets to the cups daemon. another tip: tail -f /var/log/cups/error_log in one terminal do your tests in another terminal. tail - looks at the end of the file (cf head for the top) -f = follow - as the file grows scroll it in your window. you can fiddle in one terminal and watch the logged result in the other. (when you are sick of it scrolling past, ctrl-c stops it) well it doesn't solve your problem - what is LogLevel set at in /etc/cups/cupsd.conf? And if you changed it, did you restart cupsd? are there other cups (success?) logs? what happens in the logs when the other successful machine prints? > > =====Andrew > > > On Sun, 2003-08-03 at 08:46, Nick Rout wrote: > > service should (needs?) to be run as root, and root's path should > > include /sbin. (service status may not need root permissions, > > stop|start|restart should) > > > > hint: if you are using su to get a root prompt, use su - > > > > the - loads root's environment, including the extended path. > > >
