userscript 0.21 08/01/25 - permanently include your mods

[frankmcg]

Sorry for going off-topic. Think I've sorted it out now - it requires copying the o/s back onto the USB stick to make any changes work when using the spindown script.

Back on topic, would you be able to tell be briefly how I set up the path script? Do I copy the example file called path into the /config directory and the example in the scripts directory called path.sh into the /script directory? Which file do I edit to add new paths? Thanks

[skara]

Back on topic, would you be able to tell be briefly how I set up the path script? Do I copy the example file called path into the /config directory and the example in the scripts directory called path.sh into the /script directory? Which file do I edit to add new paths? Thanks

As descriped at the wiki path.sh has to be placed in scripts/ path has to be placed in config/
To add /mnt/ide1/ and /mnt/ide2/ you have to modify config/path this way:

/mnt/ide1:/mnt/ide2

The first path is "normal". Every further path has to be given with leading ":" ! That's all.

greetz
skara

[frankmcg]

Working now, thanks for your help on that.

One further thing I've been trying but doesn't seem to be working is to add a script to kill S90Crond as this process seems to prevent my drives spinning down even with the USB spin-down fix.

I've created a new script called crond.sh to achieve this, with the code as follows:
#!/bin/sh
/etc/rc.d/...path to/S90crond.sh stop


Any idea why this doesn't seem to do anything - the process is still running after a reboot. Killing it manually by typing in the above command works fine.

[skara]

Working now, thanks for your help on that.

One further thing I've been trying but doesn't seem to be working is to add a script to kill S90Crond as this process seems to prevent my drives spinning down even with the USB spin-down fix.

I've created a new script called crond.sh to achieve this, with the code as follows:
#!/bin/sh
/etc/rc.d/...path to/S90crond.sh stop


Any idea why this doesn't seem to do anything - the process is still running after a reboot. Killing it manually by typing in the above command works fine.

I suppose, you understand what userscript does?
The NAS writes all stuff from internal flash back at boottime so all modifications are gone inclusive every startups. They run everytime!
So userscript runs scripts at every boottime to do the wished modifications! If you want any buildin service to stop you have to include your stop-command for every boottime.

You did include your own crond.sh into userscript? Does it work - maybe include a little test like 'touch /tmp/crond.sh.tmp' and look after it after booting (ls -al /tmp/crond*)?

greetz
skara

[frankmcg]

Thanks. Yes I understand how userscript is working and that it makes changes after booting that can't otherwise be saved.

I did you test and that crond.sh.tmp file is appearing in the tmp folder, so my .sh file is definitely being read. The S90crond isn't stopping though - perhaps the script stops it but then the system restarts it again?

[skara]

Maybe you should workout the crontab-stuff.
So cron can run but shouldn't to the naughty diskaccesses.
You looked after the spindown solutions at this board? There it's writen down how this can be overcome. (Even if it's german, it should be clear what to do. I think there's an translation of it at our english wikisite)

greetz
skara

[threepwood]

It seems the package is no longer available at rapidshare.
Could someone upload it somewhere, or e-mail me the package?
I would appreciate it very much.
Thank you.

EDIT:
My bad. I used a download manager, and it seems that was the problem.

[skara]

hello skara,
sorry for private message but it seem's i'm not allowed to post an answer to your topic.
I have installed userscript but seems that no script is launched during startup, I think because even init and init.us are not launched. In my installation the files are in this path:
/mnt/md1/public/applications/userscript/init and
/mnt/md1/public/applications/userscript/init.us
Only the directory userscript is created under /usr directory, but no subdirectory nor files are copied.
Can you help me pls?

best regards, ciao

Augusto

Don't know why you shouldn't be able to post here but nevertheless.

If the directory /usr/userscript exists after boot at least the init ran. BTW the folder isn't copied but linked. So whatever is done in applications/userscript/ will be done in /usr/userscript/ and vice versa.
So take a lookin both. It's impossible that one of them differs from the other.

Did you put any of the example scripts into scripts/ ?
Checkout linkroot for instance.

At last i suppose you're using latest firmware don't you?

greetz
skara

[The Rider]

[solved!]
hello, thanks for answer....
I got the problem. Seeding some "echo >>" statement along the script I've seen that both the scripts are executed but the problem was in my own script where I attempted to launch rsync not specifying the full path of rsync executable.
so changing the previous statement in the script

rsync --daemon ...........

with

/mnt/md1/public/applications/local_apps/bin/rsync --daemon ........

works fine

thanks again

[wenze]

Hello,

i will change the mount option for the hdd on my NAS. I use Raid 1.
How can i do this with this script?

thx