Hello.
On Thu, 2007-02-01 at 10:48, Dan Williams wrote:
> On Thu, 2007-02-01 at 14:44 +0100, Stefan Schmidt wrote:
> >
> > I even wrote a wrapper around wpa_supplicant to always give me -dd
> > output, but it seems nm not even start to communicate with the
> > supplicant.
>
> If you edit the code in nm-device-802-11-device.c, in supplicant_exec():
>
> - char * argv[4];
> + char * argv[5];
> GError * error = NULL;
> GPid pid = -1;
> int sup_stdout;
>
> argv[0] = WPA_SUPPLICANT_BIN;
> argv[1] = "-g";
> argv[2] = WPA_SUPPLICANT_GLOBAL_SOCKET;
> - argv[3] = NULL;
> + argv[3] = "-ddd";
> + argv[4] = NULL;
I have already the following in src/nm-device-802-11-wireless.c:
supplicant_exec (NMDevice80211Wireless *self)
{
gboolean success = FALSE;
char * argv[5];
GError * error = NULL;
GPid pid = -1;
int sup_stdout;
argv[0] = WPA_SUPPLICANT_BIN;
argv[1] = "-dd";
argv[2] = "-g";
argv[3] = WPA_SUPPLICANT_GLOBAL_SOCKET;
argv[4] = NULL;
No src/nm-device-802-11-device.c here.
> That will then make NM log everything that wpa_supplicant prints to
> stdout and stderr, to the normal place that NM logs things. If you run
> NM as root with --no-daemon, it will go to your terminal.
>
> We really need to get your NM output here to see what the problem is.
That's why I posted links to the first logs. There was no change in
the logs today.
regards
Stefan Schmidt
Attachment:
signature.asc
Description: Digital signature