Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No iwgetid on Linux #9

Open
joepie91 opened this issue Jul 13, 2015 · 5 comments
Open

No iwgetid on Linux #9

joepie91 opened this issue Jul 13, 2015 · 5 comments

Comments

@joepie91
Copy link

The following happens, seems like it's trying to use a tool that's not (always) installed by default:

sven@linux-etoq:~> wifi-password
spawn iwgetid ENOENT

Platform: openSUSE 13.1, x86_64, XFCE

@kevva
Copy link
Owner

kevva commented Jul 13, 2015

Do you know of any other way in your distro? iwgetid is widely available by default on many distros as far as I know.

@joepie91
Copy link
Author

It actually seems that I do have iwgetid, but...

sven@linux-etoq:~> iwgetid
Absolute path to 'iwgetid' is '/usr/sbin/iwgetid', so running it may require superuser privileges (eg. root).

... so that is probably why. It does seem to run fine without root, though, when explicitly specifying the path.

sven@linux-etoq:~> /usr/sbin/iwgetid
sven@linux-etoq:~>

(there's no WiFi on this particular machine, it returns a valid value on my laptop though, in the same environment)

@kevva
Copy link
Owner

kevva commented Jul 13, 2015

So, I guess it works then :). Weird that it reports ENOENT though.

@kevva kevva closed this as completed Jul 13, 2015
@joepie91
Copy link
Author

Well, not quite. It seems to get stuck on it not being in /usr/bin - I'm not really sure how openSUSE handles this all. I still get the same error on my laptop, since it never actually calls /usr/sbin/iwgetid.

@kevva kevva reopened this Jul 13, 2015
@joepie91
Copy link
Author

A possibly related issue; linux-wifi-password uses this code, but:

  1. This does not seem to take into account situations where not NetworkManager is used, but another manager (eg. wicd), and
  2. I'm not sure whether execFile passes through stdin/stdout - most distributions do not have passwordless sudo (I am assuming that you've tested this module primarily on Ubuntu).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants