@PeterT: Nah, wpa-supplicant is started from ~nickel/KOReader/KSM when enabling WiFi
.
On a sidenote, nickel seems to be using dhcpcd instead of udhcpc nowadays, but that's another thing entierely ^^.
But it definitely shouldn't have a hold on fonts, FWIW, this is with nickel's/the system's wpa-supplicant call:
Code:
/mnt/onboard/.niluje/usbnet/bin/lsof +c0 | ag wpa
dhcpcd-dbus 2153 root 9u unix 0x9eda6d00 0t0 13428 /tmp/dhcpcd-dbus-wpa-2153.0 type=DGRAM
dhcpcd-dbus 2153 root 10u unix 0x9eda6680 0t0 13430 /tmp/dhcpcd-dbus-wpa-2153.1 type=DGRAM
wpa_supplicant 2160 root cwd DIR 179,1 1024 2 /
wpa_supplicant 2160 root rtd DIR 179,1 1024 2 /
wpa_supplicant 2160 root txt REG 179,1 385184 32819 /bin/wpa_supplicant
wpa_supplicant 2160 root mem REG 179,1 97580 934 /lib/ld-2.11.1.so
wpa_supplicant 2160 root mem REG 179,1 266828 672 /usr/lib/libssl.so.0.9.8
wpa_supplicant 2160 root mem REG 179,1 1138080 666 /usr/lib/libcrypto.so.0.9.8
wpa_supplicant 2160 root mem REG 179,1 9816 788 /lib/libdl-2.11.1.so
wpa_supplicant 2160 root mem REG 179,1 881932 752 /lib/libc-2.11.1.so
wpa_supplicant 2160 root 0u CHR 1,3 0t0 145 /dev/null
wpa_supplicant 2160 root 1u CHR 1,3 0t0 145 /dev/null
wpa_supplicant 2160 root 2u CHR 1,3 0t0 145 /dev/null
wpa_supplicant 2160 root 3u unix 0x9eda6b60 0t0 13392 type=DGRAM
wpa_supplicant 2160 root 4u sock 0,5 0t0 13393 can't identify protocol
wpa_supplicant 2160 root 5u netlink 0t0 13394 ROUTE
wpa_supplicant 2160 root 6u pack 13398 0t0 34958 type=SOCK_DGRAM
wpa_supplicant 2160 root 7u unix 0x9eda7520 0t0 13400 /var/run/wpa_supplicant/eth0 type=DGRAM