Timeline for No output when running script on startup (but correct output if run manually)
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 8, 2016 at 11:37 | comment | added | Torxed | @nieswand pleasure was all mine! Welcome to Stack Unix btw. Best of luck | |
| Jan 8, 2016 at 11:36 | vote | accept | nieswand | ||
| Jan 8, 2016 at 11:36 | comment | added | nieswand | That was an error on my end. sleep now works for me. Since it is just a small feature that might be replaced with something more suitable as soon as I learn a bit more about Linux, this quick fix will do. Thanks a lot! Since I'm new to this: Should I change the question? Because the actual problem changed somewhat during the discussion. | |
| Jan 8, 2016 at 1:14 | comment | added | nieswand | I followed the instructions given on the page you linked to. It changes nothing on the outcome of my script. I also added a sleep time, but no matter how long I let the script sleep, the outcome is always the same. In fact, I can't log in via ssh during the sleep time. So it seems that the setup of the IP is delayed until after my script has finished. So sleeping is not a solution | |
| Jan 7, 2016 at 13:14 | history | edited | Torxed | CC BY-SA 3.0 | added 1328 characters in body |
| Jan 7, 2016 at 13:05 | comment | added | nieswand | I'm using root's crontab -e. I added whoami and ip addr to crontab -e, etc/rc.local, and /etc/network/if-up.d/sayhi (one after another) and they all yield root as user. The ip.log in all three cases tells me that eth0 is down and has no local IP, yet. Even the if-up.d script. I also added post-up /etc/network/if-up.d/sayhi to the eth0 interface in /etc/network/interfaces. Still, ip.log says eth0 is down. BUT: If I only restart my network connection (and not the Pi itself) with sudo /etc/init.d/networking restart, then eth0 is shown as up in ip.log | |
| Jan 6, 2016 at 23:55 | comment | added | Torxed | @nieswand You are correct, that should be the private file! Humm, this is most peculiar. under which crontab -e are you doing this? Can you, in your script do whoami > ~/whoami.log and check that file for the users name? Are you sure this script is being run after your have your network up? You can double-check this by adding ip addr > ~/ip.log at the top of your script. Remember the RPi is quite slow so it might be that the DHCP havn't fully gotten an IP yet. | |
| Jan 6, 2016 at 21:41 | comment | added | nieswand | Unfortunately, neither of those options works. Also: the identify file (-i) should be the private key, right? | |
| Jan 6, 2016 at 15:33 | history | answered | Torxed | CC BY-SA 3.0 |