OpenBSD 4.2 - Can only run an app as user

As the title implies, I've got an application here that I can't run as root. I'm pretty new to *nix in general, but I've put aside a harddrive to give OpenBSD a go.

I've installed wpa_supplicant through the packages (binary tree/pkg_add) and when run as a user, I don't have the priveleges to access the wireless card. SU to root, and the system can't find the wpa_supplicant executable. I've installed a fair few things already, and this is the first time I've seen this. I googled it, but no luck.

Thanks to anyone who can even point me in the right direction.

[Prometheum]

OpenBSD is pretty much the worst place to start using unix at. I would recommend FreeBSD first while you get a feel for stuff, and when you're ready, upgrade to OpenBSD.

Yeah, I've heard the same a fair bit, but I have tried FreeBSD a little in the past and OpenBSD appeals to me more. I don't care that it's difficult as I have a Win drive here if I REALLY need to do anything, but I've got almost everything I need 'working' regardless and I'm now trying to get into the mechanics of the system.


That said, I've got a bit more detail on the problem - I've found the executable and added the PATH into both root and my main user's .profile file, and it works fine if I log in as either user - the problem comes up when I su though, because when I echo $PATH it doesn't return all of the items.

In short: if I su to root, my PATH variable doesn't contain all of the locations defined in the .profile file - any ideas?

[oddballz194]

Originally Posted by Auschwitz - Nazi Disneyland

Yeah, I've heard the same a fair bit, but I have tried FreeBSD a little in the past and OpenBSD appeals to me more. I don't care that it's difficult as I have a Win drive here if I REALLY need to do anything, but I've got almost everything I need 'working' regardless and I'm now trying to get into the mechanics of the system.


That said, I've got a bit more detail on the problem - I've found the executable and added the PATH into both root and my main user's .profile file, and it works fine if I log in as either user - the problem comes up when I su though, because when I echo $PATH it doesn't return all of the items.

In short: if I su to root, my PATH variable doesn't contain all of the locations defined in the .profile file - any ideas?

There's probably another profile used for su-type logins. I know bash uses .bashrc as well as .bash_profile, and normally only one of those is run when you use su whereas both are run if you log in normally (though I don't remember which offhand).

You could always use the source command to run the login script though, as follows (assuming the .profile is in your home directory):

source ~/.profile