I've run into a problem in 9.1 where I call /sbin/yast2 and I never see the window that asks me for the root password. Instead I get the user-level version of YaST with reduced capabilities. However, if I summon Yast via the K menu, it gives me the query window and works correctly. On further investigation I discovered the difference between the K menu call and the explicit call: the K menu call has an option "run program as a different user". That option is checked, and the user name is blank. I also discovered that I can create a desktop object for YaST2 and the behavior there is the same: if the object specifies "run as a different user" and the user is blank, it works correctly; if "run as a different user" is unchecked, it runs only at user level. So my two questions are: 1. What exactly is the effect of "run as a different user", both in general and in the particular case where the user name is blank? 2. Is there a way to get that effect from an ordinary command line? Paul Abrahams
On Thursday, 28 October 2004 21.52, Paul W. Abrahams wrote:
1. What exactly is the effect of "run as a different user", both in general and in the particular case where the user name is blank?
In general, it will switch to the named user before the program is run, so that the program is run as that user. In the special case where the user name is blank, it defaults to the root user
2. Is there a way to get that effect from an ordinary command line?
Yes, by running kdesu yast2
From the command line do:
kdesu yast2
Osho
On Thu, 28 Oct 2004 15:52:26 -0400, Paul W. Abrahams
I've run into a problem in 9.1 where I call /sbin/yast2 and I never see the window that asks me for the root password. Instead I get the user-level version of YaST with reduced capabilities. However, if I summon Yast via the K menu, it gives me the query window and works correctly.
On further investigation I discovered the difference between the K menu call and the explicit call: the K menu call has an option "run program as a different user". That option is checked, and the user name is blank. I also discovered that I can create a desktop object for YaST2 and the behavior there is the same: if the object specifies "run as a different user" and the user is blank, it works correctly; if "run as a different user" is unchecked, it runs only at user level.
So my two questions are:
1. What exactly is the effect of "run as a different user", both in general and in the particular case where the user name is blank?
2. Is there a way to get that effect from an ordinary command line?
Paul Abrahams
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
* Paul W. Abrahams
2. Is there a way to get that effect from an ordinary command line?
In addition to kdesu, sudo will allow 'X' apps, yast2, to run from the command line as root. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos
participants (4)
-
Anders Johansson -
Osho GG -
Patrick Shanahan -
Paul W. Abrahams