new cups 1.1.x and 1.2.x and yast2
Hey Group; As a long time Unix person I have run into one thing that I can't figure out. Why is Yast2, when setting up cups it resuses to leave the permissions on /etc/cups/files as lp.lp and insists on changing them to root.lp after I set them as SuSE does lp.lp. Problem seem to be coming from Yast2 near the end of the process when it is going to write the configured data. Up pops an error message. Which causes it not to write the default printer info. I have the cups-user and group set to lp for ./configure. It looks like yast2 is the cause. Also it seem /sbin/mkinitrd is not able to figure out the correct kernel version for modules. In version 1.2.# (SuSE90^) it worked, However, in 1.9.# (SuSE 93) it seems to be broken. -- 73 de Donn Washburn Hpage: " http://www.hal-pc.org/~n5xwb " Ham Callsign N5XWB Email: " n5xwb@hal-pc.org " 307 Savoy St. HAMs: " n5xwb@arrl.net " Sugar Land, TX 77478 BMW MOA #: 4146 - Ambassador LL# 1.281.242.3256 " http://counter.li.org " #279316
Sun, 19 Jun 2005, by n5xwb@hal-pc.org:
Hey Group;
As a long time Unix person I have run into one thing that I can't figure out. Why is Yast2, when setting up cups it resuses to leave the permissions on /etc/cups/files as lp.lp and insists on changing them to root.lp after I set them as SuSE does lp.lp. Problem seem to be coming from Yast2 near the end of the process when it is going to write the configured data. Up pops an error message. Which causes it not to write the default printer info. I have the cups-user and group set to lp for ./configure.
It looks like yast2 is the cause.
You can set file permissions explicitly in /etc/permissions.local Theo -- Theo v. Werkhoven Registered Linux user# 99872 http://counter.li.org ICBM 52 13 26N , 4 29 47E. + ICQ: 277217131 SUSE 9.2 + Jabber: muadib@jabber.xs4all.nl Kernel 2.6.8 + See headers for PGP/GPG info. Claimer: any email I receive will become my property. Disclaimers do not apply.
Hello, On Jun 19 12:25 Donn Washburn wrote (shortened):
As a long time Unix person I have run into one thing that I can't figure out. Why is Yast2, when setting up cups it resuses to leave the permissions on /etc/cups/files as lp.lp and insists on changing them to root.lp after I set them as SuSE does lp.lp. Problem seem to be coming from Yast2 near the end of the process when it is going to write the configured data.
It is not YaST. It is the cupsd which takes care that owner and group are set as specified in its config file and that the permissions are set sufficiently secure. To verify it, change for example owner group and permissions of /etc/cups/printers.conf and then stop and start the cupsd.
Up pops an error message. Which causes it not to write the default printer info. I have the cups-user and group set to lp for ./configure.
What do you mean with "./configure"? Do you use self-compiled software? If yes, you must tell this and of course which exact version and which ./configure options and all the rest. Otherwise nobody can help you because nobody knows what you did. In general you are on your own when you self-compile your software. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsmeix@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/
participants (3)
-
Donn Washburn -
Johannes Meixner -
Theo v. Werkhoven