Vous n'êtes pas connecté.
Pages: 1
Good evening out there,
i can't get to the solution of the following problem, that arised with update to SliTaz 4:
up to now, I started a (sort of) frugal installation that invoked a script (called mozilla.sh) from /etc/init.d/local.sh (where users scripts should be put). The script takes an original download of the latest firefox (in .tar.bz2) and unpacks it to /usr/lib/firefox.
As stated, up to SliTaz 3 this worked like a charm.
In SliTaz 4 the script is started (as I see files of about 10 MB in the otherwise non-existent /usr/lib/firefox -folder) but stops during the process (I presume when the boot-up-process is finished).
Since I start the script with "nohup [path]/mozilla.sh &" I can't see why the process is killed (and I don't find any evidence in the logfiles, neither in /nohup.out, although a much faster script exits fine and another quite slow script isn't finished either).
Installing coreutils-command (for a non-busybox-version of nohup) didn't solve the problem.
Anyone an idea where to look next ?!?
Thx.
Hors ligne
I digged in a little deeper...
when I start my own script(s) directly in /etc/init.d/rcS with "nohup [path]/scrip.sh &" the script is finished as requested.
So it seems that the scripts called in /etc/init.d/local.sh either slow down the boot process (letting the rest wait for it to finish) or have to be called with nohup in the startup script directly since they will die when /etc/init.d/rcS is finished.
So problem might be considered as solved.
Hors ligne
Pages: 1
[ Généré en 0.017 secondes, 7 requêtes exécutées - Utilisation de la mémoire: 1.53 MiO (Pic : 1.77 MiO) ]