Can't get Init script to run

[lmannyr]

I used to have this fan script automatically start and stay running on boot. After several truNAS upgrades....it is no longer running. Running "PS" in shell does not show it running. I can manually run it in shell...but when shell is shut down....the script is shut down. I need it to run on boot....and stay running. What am I doing wrong here. Path the the .sh file is correct.

 

[Samuel Tai]

Does the script have all the execute bits set? Try chmod 755 </path/to/script>.

 

[lmannyr]

Does the script have all the execute bits set? Try chmod 755 </path/to/script>.

No change. I added "999999999" to the timeout to see if I see it running once boot is complete.. If so...then I need to know how to disable the "timeout" entry for the init script setup.

 

[lmannyr]

"0" in timeout doesn't disable the "timeout" function.

 

[Samuel Tai]

What are the contents of the script? It could be something simple, like needing to specify the full paths of any executables in the script.

 

[lmannyr]

What are the contents of the script? It could be something simple, like needing to specify the full paths of any executables in the script.

Fan Scripts for Supermicro Boards Using PID Logic

hello, i found that thread via https://www.truenas.com/community/threads/fan-scripts-for-supermicro-boards-using-pid-logic.51054/page-13#post-551335 posted on reddit. not sure ... but i have supermicro X11SSL-F and noctua 3x nf-s12b redux 1x NF-a14 pwm. Basically i tried some hacks via ipmi...

www.truenas.com

Above is the link to the script. It has ALWAYS worked. Still works now if I manually start it in shell. For the meantime, I have it running under TMUX just fine. It just wont run in "INIT". There is a TIMEOUT entry in the INIT setup. The timeout help says it is the amount in seconds until the script is terminated. So, what do I put in the TIMEOUT section if I DON"T want it to terminate and would rather it run indefinitely?

 

[Patrick M. Hausen]

You write

Code:

#!/bin/sh

(
# your code
# that should run
# forever
) >/dev/null 2>&1 &

exit 0

 

[lmannyr]

You write

Code:

#!/bin/sh

(
# your code
# that should run
# forever
) >/dev/null 2>&1 &

exit 0

Write that where? In the "timeout" section of the init setup? really?

 

[Patrick M. Hausen]

No,that's what you put in your script. Enclose all the code you want to keep running in parentheses () and add a & at the end --> background job. So the script you use as an init task can exit but the code you need to run keeps running, Shell programming 101 ...

 

[lmannyr]

No,that's what you put in your script. Enclose all the code you want to keep running in parentheses () and add a & at the end --> background job. So the script you use as an init task can exit but the code you need to run keeps running, Shell programming 101 ...

I'll give it a shot. No programming ed here, but can get around with some guidance. Thanks!!

 

[lmannyr]

No,that's what you put in your script. Enclose all the code you want to keep running in parentheses () and add a & at the end --> background job. So the script you use as an init task can exit but the code you need to run keeps running, Shell programming 101 ...

This worked. Thank you sir.

 

[lmannyr]

This worked. Thank you sir.

I take this partly back. This will keep it running if ran under shell/ssh etc and exiting. TMUX not needed. But still does not work as a TRU NAS Core Post init task. Its still not running after a reboot.

 

[sretalla]

If you want to be able to interact with the script while it continues running I would suggest running it with tmux as I mention in the edit at the bottom of this post:

OpenCorsairLink in a jail to control fans?

I have had another look at this and was finally able to compile the official project (https://github.com/audiohacked/OpenCorsairLink) on a stock FreeBSD 12 install which I will do a bit more to document in the next little while and will also update the script to use the latest updates to @Kevin...

www.truenas.com

That also conveniently gets around the need to deal with timeouts, as it effectively exits from the launcher just like a command with "&" at the end.

 

[lmannyr]

If you want to be able to interact with the script while it continues running I would suggest running it with tmux as I mention in the edit at the bottom of this post:

OpenCorsairLink in a jail to control fans?

I have had another look at this and was finally able to compile the official project (https://github.com/audiohacked/OpenCorsairLink) on a stock FreeBSD 12 install which I will do a bit more to document in the next little while and will also update the script to use the latest updates to @Kevin...

www.truenas.com

"I" dont' need to interact with the script. I need it to run in the background 24/7 post system boot. System RARELY gets a reboot, but don't want to forget to run this manually. Worked prior to all the updates as a post init task.

 

[sretalla]

"I" dont' need to interact with the script. I need it to run in the background 24/7 post system boot. System RARELY gets a reboot, but don't want to forget to run this manually. Worked prior to all the updates as a post init task.

Well, what I'm proposing IS a post init task that has worked (and still works) for me, which wraps the script in a tmux session that automatically starts as an init script... ignore it if you want.

It's also a clean way to avoid needing to reboot in order to restart/modify the script as you can just keep it going in the tmux session.

 

[lmannyr]

Well, what I'm proposing IS a post init task that has worked (and still works) for me, which wraps the script in a tmux session that automatically starts as an init script... ignore it if you want.

It's also a clean way to avoid needing to reboot in order to restart/modify the script as you can just keep it going in the tmux session.

Ah....Ok. I'll read up on the post. Thanks!