My goal was to make my Pi create its own WiFi on start so that I can connect to it wirelessly.
I have succeeded by creating a crontab entry (using sudo crontab -e):
@reboot /path/to/create_ap.sh &
where create_ap.sh is a script launching create_ap:
#!/bin/bash
sudo create_ap -n wlan0 MySSID MyPass --daemon
However, I've failed to do this without an additional script: both
@reboot create_ap -n wlan0 MySSID MyPass --daemon
and
@reboot create_ap -n wlan0 MySSID MyPass --daemon &
didn't work as expected (I've also tried to add full path, /usr/bin/create_ap like suggested in comments but that didn't help).
So does crontab allow parameters after the command? (I suspect that only @reboot create_ap bit works in practice, but failed to google that) Or is there some other problem with these lines in crontab and I can adjust them so that an external script is not needed?
create_apin your crontab work? (I believe the path is/usr/bin/create_ap). Does your crontab change thePATHvariable in any other way? – Aurora0001 Jan 1 '18 at 10:56which create_apsays/usb/bin/create_apand I've tried full path in crontab but that didn't help – YakovL Jan 1 '18 at 17:51crontab -e) one difference is that the command kicks off as your user, whereas your script includessudoto execute the command as root. This should go into a system crontab to execute as root on startup. – bobstro Jan 2 '18 at 14:38sudo crontab -eso that's root crontab, I guess. Will add this to the question – YakovL Jan 2 '18 at 18:44create_apscript in the non-working entries. Try prepending a path tocreate_ap. Check logs or email for errors. – bobstro Jan 2 '18 at 20:06