Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

powerdown schedule problem

Featured Replies

Hello,

 

I'm having trouble getting the powerdown utility to work.  I installed in via the unMenu interface and ticked "reinstall on reboot".  I then ran the command: echo "/sbin/powerdown" | at 23:00

 

That night it successfully shut down at 11pm, however the next (and subsequent days) it did not.

 

If I run the same command again, it will shut down that night, however not the next night?

 

I think I need to add the command to whatever to the linux equivalent of autoexec.bat, but alas, I have no idea how that would be done.

 

Any help appreciated!!!

 

Hello,

 

I'm having trouble getting the powerdown utility to work.  I installed in via the unMenu interface and ticked "reinstall on reboot".  I then ran the command: echo "/sbin/powerdown" | at 23:00

 

That night it successfully shut down at 11pm, however the next (and subsequent days) it did not.

 

If I run the same command again, it will shut down that night, however not the next night?

 

I think I need to add the command to whatever to the linux equivalent of autoexec.bat, but alas, I have no idea how that would be done.

 

Any help appreciated!!!

 

 

That command has to be put in your go script located in the config folder of your flash drive.  By running at the command line the computer knows it needs to do that at 11pm for that night, but when it does shut down its knowledge of that command is lost.

 

Run these commands ONCE from the command line and they will be added to your go script:

echo "" >> /boot/config/go

echo "echo \"/sbin/powerdown\" | at 23:00" >> /boot/config/go

 

This will set it up so that your computer knows it needs to shut down at 11pm on every boot.

  • Author

Prostuff,

 

Thank you very much.  I ran both the commands. 

 

I'll report back in 2 days and let you know how it goes.

 

One more question.  If I want to disable it from shutting down on schedule, how would I do it?

 

Thanks!

Prostuff,

 

Thank you very much.  I ran both the commands. 

 

I'll report back in 2 days and let you know how it goes.

 

One more question.  If I want to disable it from shutting down on schedule, how would I do it?

 

Thanks!

 

Delete the line from the config file.

Prostuff,

 

Thank you very much.  I ran both the commands. 

 

I'll report back in 2 days and let you know how it goes.

 

One more question.  If I want to disable it from shutting down on schedule, how would I do it?

 

Thanks!

Actually, you can leave it in the config file.

 

To see the queued "at" job, type

atq

The first number on the line is the job number.  Typically, it will be number 1.

To remove job #1 from the queue (so it will not execute) type:

atrm 1

(If the job number was 27, you would type atrm 27 )

to see the details of a queued job type:

at -c 1

(again replace "1" with the appropriate job number returned by atq )

 

  • Author

Hello,

 

After running both those commands, it did not shut down last night?  I'm not sure how to debug.  What information would be useful for me to post?

 

Regards!

Hello,

 

After running both those commands, it did not shut down last night?  I'm not sure how to debug.  What information would be useful for me to post?

 

Regards!

Those two commands would have appended lines to your config/go script.

 

Those lines would not be invoked to queue the shutdown until you reboot, and the "go" script is run once more  when the array first comes online.

 

So... reboot, then look at the "queue" by typing

atq.

 

If you see a job queued for 23:00 it is working.

  • Author

Thank you!

 

After reboot I see there is a job scheduled for 23:00.

 

 

  • 7 months later...
  • Author

Hello,

 

I have a follow up to my previous question here...

 

My shutdown schedule as been working fine since my last post.  I needed to disable it to run a parity check.

 

I ran the command: atrm 1

and confirmed the job was gone with: atq

 

I finished the lengthy parity check, then executed:

echo "" >> /boot/config/go

echo "echo \"/sbin/powerdown\" | at 23:00" >> /boot/config/go

 

I now have 2 powerdown jobs scheduled for 23:00.

I see the error of my ways, I know I added another identical command when I should have just rebooted to get back to the original state.

 

Can someone please tell me how to permanently remove the 2nd redundant job?

 

Much appreciated!!!

 

Hello,

 

I have a follow up to my previous question here...

 

My shutdown schedule as been working fine since my last post.  I needed to disable it to run a parity check.

 

I ran the command: atrm 1

and confirmed the job was gone with: atq

 

I finished the lengthy parity check, then executed:

echo "" >> /boot/config/go

echo "echo \"/sbin/powerdown\" | at 23:00" >> /boot/config/go

 

I now have 2 powerdown jobs scheduled for 23:00.

I see the error of my ways, I know I added another identical command when I should have just rebooted to get back to the original state.

 

Can someone please tell me how to permanently remove the 2nd redundant job?

 

Much appreciated!!!

 

edit your config/go script.  You added a second line to its end.  Remove the additional line.

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.