Tiny Core Linux
Tiny Core Extensions => TCE Q&A Forum => Topic started by: emninger on October 31, 2015, 06:35:22 AM
-
Related to how start processes automatically, looked into the FAQ and what i found there, for what i understand, that there should be scripts in
/usr/local/tce.installed
.
Especially, i want conky and tor to be started on boot. Now, there is a script (for both one). But seem to me not starter but rather installer. Should i edit those scripts adding simply a line in the end like conky -c $HOME/.conkyrc
? (Is the '-c' needed? Starting from RunProgram in the wbar, conky is sufficient, it reads the .conkyrc in the home directory and not the conky.conf which came by default).
As for tor: Will tor look automatically to the $HOME/.tor/torrc?
Thanks al lot for your patience!
-
For Conky, -c $HOME/.conkyrc is not needed.
I start Conky from ~/.X.d/60-conky
conky -p 2 -d -b -o >/dev/null 2>&1 &
The file doesn't need a line break nor does it need to be executable as it's sourced from ~/.xsession .
-
For things that don't need X, you can use /opt/bootlocal.sh
sleep 1 && [ -e /usr/local/sbin/basic-firewall ] && /usr/local/sbin/basic-firewall noprompt >/dev/null 2>&1 &
-
For Conky, -c $HOME/.conkyrc is not needed.
I start Conky from ~/.X.d/60-conky
conky -p 2 -d -b -o >/dev/null 2>&1 &
The file doesn't need a line break nor does it need to be executable as it's sourced from ~/.xsession .
The '-o' is needed even if there is a window definition in the conkyrc? I start conky simply by conky -d ...
-
No, sorry. Actually none of those are needed. I have own_window in my config, too.
-p can help sometimes though.
-
Comes up to my mind: Since i use fluxbox, not flwm, could i set this processes in the fluxbox startup file as well?
-
For things that don't need X, you can use /opt/bootlocal.sh
sleep 1 && [ -e /usr/local/sbin/basic-firewall ] && /usr/local/sbin/basic-firewall noprompt >/dev/null 2>&1 &
Just out of curiousity and to learn something linuxwise: For what it's good the ">/dev/null 2>&1" part?
-
Just out of curiousity and to learn something linuxwise: For what it's good the ">/dev/null 2>&1" part?
A quick search gave me 914,000 results :D
-
Got it ;)
-
Comes up to my mind: Since i use fluxbox, not flwm, could i set this processes in the fluxbox startup file as well?
No, *box'es are getting started in a way where those WM specific startup/autostart scripts won't be used.
/opt/bootsync.sh , /opt/bootlocal.sh and especially ~/X.d/* should be everything you need though. Also it's independent from the Window Manager in use. So you can try another WM without missing your auto-starting programs.
-
Thanks!!!
And thanks for your patience - you're a good teacher! :D