I played with Cups about a month ago, here are my thoughts > > I've done a fresh cvsup of the ports system this morning to > get the latest parts of the CUPS system. > > make and make install went fine and I have launched the cupsd > via /usr/local/etc/rc.d/cups.sh start > > Problems start occurring at this point. Here are the issues I'm > having: > > 1. CUPS does not see my parallel ports. > > # dmesg | egrep -i 'lp|parall' > ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0 > lpt0: <Printer> on ppbus0 > lpt0: Interrupt-driven port > ppi0: <Parallel I/O> on ppbus0 > ppc1: <Parallel port> at port 0x278-0x27f irq 8 on isa0 > lpt1: <Printer> on ppbus1 > lpt1: Interrupt-driven port > ppi1: <Parallel I/O> on ppbus1
I had the same problem with the parallel port. I had to reboot the machine with the printer plugged in and turned on for it to show up. > > 2. CUPS http interface "broke" > > If I point a browser at the CUPS host: > http://cupsserver:631/admin > I see the admin page, but the navbar across the top is missing, > all I see is the ALT text. The cups /var/log/cups/access_log > shows 403 errors for all /images/*gif. > > > When I attempt to add a new printer via http interface > by issuing > > http://cupsserver:631/printers > > The browser returns an alert... > > The document contains no data > > and the /var/log/cups/error_log says... > > W [03/Feb/2003:12:11:16 -0600] Possible DoS attack - > more than 10 clients connecting from 172.16.1.33! > W [03/Feb/2003:12:11:16 -0600] Possible DoS attack - > more than 10 clients connecting from 172.16.1.33! > W [03/Feb/2003:12:11:16 -0600] Possible DoS attack - > more than 10 clients connecting from 172.16.1.33! > W [03/Feb/2003:12:11:16 -0600] Possible DoS attack - > more than 10 clients connecting from 172.16.1.33! I did not have this problem, sorry. I would suggest you double check which hosts you are allowing to connect. There are 2(?) spots in the cupsd.conf file to check/change depending on if you are using it as a headless server (like me) or a desktop. Wouldn't be a bad idea to limit it with hosts.allow too. > > If I try to add a new printer with the URL: > http://cupsserver:631/admin/?op=add-printer I go to the next page of the "wizard" and fill in the printer form, but a submission returns the same errors as above. 3. Cannot add printers via CLI: If I try to add a new printer from a CLI, I see... # lpadmin -p LaserJet -E -v parallel:/dev/lpt0 -m laserjet.ppd lpadmin: add-printer (set device) failed: client-error-not-possible I got the 'client error not possible' when I was trying to force cups to recognize the parallel printer before I had restarted the computer, but this was still via the web interface. the /var/log/cups/error_log reports: I [03/Feb/2003:12:20:52 -0600] New printer 'LaserJet' added by 'root'. E [03/Feb/2003:12:20:52 -0600] add_printer: bad device-uri attribute 'parallel:/dev/lpt0'! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
