Timeline for Autorun c executable on boot
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 30, 2016 at 21:58 | vote | accept | JJT | ||
| Aug 30, 2016 at 13:58 | comment | added | goldilocks | "I then created a bash script called temp_logger.sh in /etc/init.d with the right header from /etc/init.d/skeleton..." -> Don't go down this road. That pattern is applicable to SysV init, for which there is a long history of documentation since it was the default used on Debian up until last year, when they switched to systemd. They were the final hold out among major GNU/Linux distros in this regard so SysV, although it still has legacy support, is now effectively defunct. I.e., don't waste your time learning how to use an obsolete tool. | |
| Aug 30, 2016 at 11:45 | answer | added | goldilocks | timeline score: 1 | |
| Aug 30, 2016 at 10:25 | comment | added | Ghanima♦ | Hello and welcome. I'll not rush to close this as a dupe. However, please mind that there are multiple answered questions with respect to how to execute a program on boot. From your description, and just as Milliways suggests, this sounds more like an issue with your program in the first place and the task is to debug that. Please provide more input. | |
| Aug 30, 2016 at 9:49 | comment | added | Milliways | /home/pi/temp_logger/./temp_logger doesn't make sense. bash will ignore the "." - not sure about cron. What source language the executable was written in is irrelevant, but without seeing your code no one can tell what it may be doing. | |
| Aug 30, 2016 at 9:32 | history | edited | JJT | CC BY-SA 3.0 | added 192 characters in body |
| Aug 30, 2016 at 9:24 | answer | added | Varad A G | timeline score: 1 | |
| Aug 30, 2016 at 9:20 | review | First posts | |||
| Aug 30, 2016 at 9:31 | |||||
| Aug 30, 2016 at 9:19 | history | asked | JJT | CC BY-SA 3.0 |