I upgraded my wife's computer and my Sister-in law's computer to slackware64-current (from Vista, two more converts). I use a script I created to connect to the various wireless networks we use. I use the script directly at the command line on my machine. I created a KDE shortcut on the ladies computers. If I run the script from their command line (sudo autoWireless) it will connect as expected. If I use the shortcut that I created It does not connect. All the components of the script are setup properly in the sudoers file for use without a password. The command i put into the KDE shortcut is "sudo autoWireless", same thing I use on the command line. Is there something about using sudo directly in a shortcut in KDE that does not work?

In the shortcut properties, try using kdesu rather than sudo.

Or, you can add that command to the /etc/sudoers file. This way they won't have to enter (or know) the root password.

you may also try the "wicd" from the /extra directory.
it is quite a nice wireless manager, that can save your preferred connections and do the auto connecting. as well as having a systray GUI application allowing them select additional networks while they're roaming.

take care,

vb

Woodsman, thanks I'll give it a try. Does this prompt for a password if NOPASSWD is set in the sudoers file?

manwichmakesameal, This is already the case. The problem is that the script does not seem to function properly when run from a KDE shortcut.

vbatts, I have never gotten wicd to function properly. It was always flaky at best, probably why it is in /extra and not part of the defualt install.

Using kdesu does require providing root's password. I never have tested adding a KDE app to the sudoers list and then using kdesu. That's a good question and I might experiment later to find the answer.

see SUAUTH(5)

OK so sudo works just fine if you spell the command properly