Le mar 05/08/2003 � 02:41, Leon Brooks a �crit : > On Mon, 4 Aug 2003 19:29, Buchan Milne wrote: > > You see, instead of making it easy for a user to log in as > > root to do tasks, we must remove the necessity for them to do the > > tasks ... > > Agree. The one task which my wife needs a root password to do is printer > management. If it were possible to avert this OOtB, that would be good.
sudo but it's true that for example just to clean & align inkjet head printers u need raw access to the device, so root privileges. And sudo may not be always the solution. My experience : a workstation with NFS /home. only one local user : root. If I want the secretary to be able to clean her printer, I put kups and mtink ( the printer is an Epson SC 1160 ) in sudo with root rights, without password. mtink is right, the pb is kups. If she launch the sudoed kups, it won't work ( unable to create socket or find DCOP bla bla bla ). If I want this work, I have first to launch kups as root, and after if she launch the sudoed kups it will works ! so for me no interest because I will have to launch kups as root ( with su ) at least one time before she launch the sudoed kups if she has reboot the computer. The pb seems to be that when launch with sudo, kups try to make DCOP socket as root but in the home directory of the user, but as on NFS share root <=> nobody , no way. When i launch kups after a su, it create the DCOP in the root directory, when the user launch the sudoed kups, it take this DCOP or at least is able to run.
