Re: Starting Cups

	In my blunderings, I have determined the following

1) http--- 631 starts the cups configuration tool (Web based)
       this often fails
      a) firewall/proxy problems
     b) not understood problems with connecting - often I
           do the configuration by editing the config files directly

2) configuring network printers 
        a) firewalls, permissions etc
        b) protocol errors - I never can figure out which choice
                  to use and have a working config file up on the 
		screen as a cheat sheet.


cups itself is run by the cupsd  which can be started
  in the usual way by  /sbin/service restart cups (no d!)
  it can also be started from the configuration tool and is
usually in the init list 

	I have found this only slightly less frustrating than
     trying to get lpd configured.  
	Oh yes, I was told by
    a witch doctor to remove all traces of lpd before installing
    cups - eg rpm -e  "anything that looks like lpd". Then 
	rpm -i "anything to do with cups".  This does seem to
     reduce the number of mysterious problems.