Skip to main content

Timeline for Run script on terminal at startup

Current License: CC BY-SA 3.0

14 events
when toggle format what by license comment
Jan 22, 2019 at 0:03 history bumped CommunityBot This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Nov 9, 2017 at 3:05 review First posts
Nov 9, 2017 at 3:49
Nov 3, 2017 at 20:04 comment added Aurora0001 Perhaps try the full path of Chromium (/usr/bin/chromium-browser) instead? Maybe the PATH isn't as expected.
Nov 3, 2017 at 20:02 comment added D. Appresti I tried and it still doesn't work
Nov 3, 2017 at 19:37 comment added Aurora0001 Have you tried deleting the existing code and just using your script, then exit 0? Maybe that would work if there's an error that we've not noticed earlier in the script?
Nov 3, 2017 at 17:03 history edited D. Appresti CC BY-SA 3.0
added 624 characters in body
Nov 3, 2017 at 16:13 answer added Zombie_Pigdragon timeline score: 1
Nov 3, 2017 at 15:33 comment added D. Appresti Ok I'll do it ASAP
Nov 3, 2017 at 15:32 comment added Aurora0001 If chromium-browser doesn't run, either: rc.local isn't running at all (not likely); an error occurred before that line so the script stopped (possible) or the error occurred on that line. Could you edit to include your full rc.local?
Nov 3, 2017 at 15:29 comment added D. Appresti But chromium-browser won't start anyway and it does not need the path, right? I think there's a problem with rc local how can I test it?
Nov 3, 2017 at 15:27 comment added D. Appresti Ok, mine is a script that gives a live output about its status, and it would be better if I could see it, so, yes I'd like my terminal to be interactive, but actually I'm trying to debug a script that isn't working (when it times out I reboot the system and that's why I need it to run at startup). I also need to open chromium at startup and, since crontab can't open GUI programs, I thought that opening a terminal and writing chromium-browser automatically at startup would be the best solution. What do you suggest?
Nov 3, 2017 at 15:26 comment added Aurora0001 Also, I'd conjecture that the issue is cd path, ./script. Replace those two lines with the full path of your script e.g. /home/user/script instead and test it again. Let me know if that works so I can post a full answer for you.
Nov 3, 2017 at 15:19 comment added Aurora0001 Do you really want the terminal to be interactive (i.e. as if you typed it into a new terminal), or are you just trying to debug why your script isn't working but would otherwise be happy for it to run in the background?
Nov 3, 2017 at 14:31 history asked D. Appresti CC BY-SA 3.0