shutdown at specific date





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{
margin-bottom:0;
}








11















I know that you can schedule a shutdown for a specific time via shutdown -h 21:45 and that you shouldn't use crontabs for such things because of their repetitive nature. How can I schedule a shutdown for a specific date like 31st of August at 20:00pm?










share|improve this question































    11















    I know that you can schedule a shutdown for a specific time via shutdown -h 21:45 and that you shouldn't use crontabs for such things because of their repetitive nature. How can I schedule a shutdown for a specific date like 31st of August at 20:00pm?










    share|improve this question



























      11












      11








      11


      1






      I know that you can schedule a shutdown for a specific time via shutdown -h 21:45 and that you shouldn't use crontabs for such things because of their repetitive nature. How can I schedule a shutdown for a specific date like 31st of August at 20:00pm?










      share|improve this question














      I know that you can schedule a shutdown for a specific time via shutdown -h 21:45 and that you shouldn't use crontabs for such things because of their repetitive nature. How can I schedule a shutdown for a specific date like 31st of August at 20:00pm?







      ubuntu shutdown






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked May 26 at 22:50









      HdM UploadHdM Upload

      615 bronze badges




      615 bronze badges

























          6 Answers
          6






          active

          oldest

          votes


















          6
















          Recent Ubuntu versions use systemd and when the conventional atd and associated at scheduler for one-off commands is either not installed or not running a one-off command can be scheduled with systemd-run which is somewhat easier than manually generating a systemd timer:



           systemd-run --on-calendar="2019-08-31 20:00:00 CET" /sbin/shutdown now





          share|improve this answer





















          • 2





            The irony is that starting an entire service to do this is almost superfluous. systemd's shutdown mechanism itself supports arbitrary points in time. Its command-line tool simply does not provide the ability to access this, because it is not up to par with the command line of the BSD shutdown. As I wrote in another answer, you who want this could try persuading the systemd people to make their shutdown tool more capable, with syntax of decades' standing, rather than going around the houses with systemd-run.

            – JdeBP
            May 28 at 7:11













          • I get Invalid calendar spec: 2019-08-31 20:00:00 CET

            – HdM Upload
            Jun 2 at 14:44



















          12
















          The at command is for scheduling one off future executions.



          e.g.



          % at 8pm Aug 31
          at> echo hello
          at> <EOT>
          job 161 at Sat Aug 31 20:00:00 2019


          (the "<EOT>" was produced by pressing control-D)



          % atq
          161 Sat Aug 31 20:00:00 2019 a sweh


          You can put your shutdown command here.






          share|improve this answer


























          • Yes! I had forgotten about at when I posted - at is definitely meant for this in general, although in a company the accepted method may be at or cron, depending on conventions related to configuration management/deployment.

            – flow2k
            May 27 at 4:57











          • It is not exactly equivalent, note. unix.stackexchange.com/q/465322/5132

            – JdeBP
            May 27 at 8:15











          • at is also able to take commands from a pipe: echo "echo yup > $(tty)" | at now.

            – mosvy
            May 27 at 23:19



















          7
















          While at is the obvious way to do this, I think it will survive shutdowns, so if the machine reboots before the scheduled shutdown, it might shutdown again at the scheduled time. Therefore, using bash and GNU date we can use a delayed shutdown.



          /sbin/shutdown +$(( ( $( date -d "30 may 2019 13:15" +%s ) - $( date +%s ) ) / 60 + 1 ))



          NB: This is only accurate to one minute. It works by converting the scheduled time, and now to seconds since the UNIX epoch, calculating the difference, converting to minutes, and then using this as the delay to shutdown. It won't work correctly if the scheduled time is in the past.






          share|improve this answer

































            3
















            You use a better shutdown command.



            The van Smoorenburg, Upstart, and systemd shutdown commands do not allow a date specification. But the BSD shutdown command takes a date value in its specification of when to shut down, in the form yymmddhhmm. This has been the case ever since 4BSD, and remains so with FreeBSD and OpenBSD. NetBSD extended it to ccyymmddhhmm.



            Because the nosh toolset is also usable on the BSDs, I gave my shutdown command the same capability, extending it to CCYYMMDDHHMM per NetBSD. And because the nosh toolset is also usable on Linux, that gives Linux a shutdown command that takes dates.



            It of course works with the nosh system-manager. It also works with some other systems. It sends signals to process #1 to enact stuff and the same signals are understood by some other system managers, such as systemd, which can also be shut down using it.



            You could use it, or a tool like it; or you could try to persuade the authors of other Linux shutdown programs to extend their tools to also be as capable as the BSD shutdown.



            Further reading




            • Jonathan de Boyne Pollard (2018). shutdown. nosh toolset manual pages. Softwares.

            • Jonathan de Boyne Pollard (2018). system-manager. nosh toolset manual pages. Softwares.


            • shutdown. System Manager's Manual. NetBSD Manual pages. 2011-11-04.


            • shutdown. FreeBSD System Managers' Manual. 2018-01-01.


            • shutdown. OpenBSD Manual pages. 2015-01-21.

            • https://unix.stackexchange.com/a/465337/5132






            share|improve this answer

































              1
















              To run the job only this year:



              0 20 31 8 * test $(/bin/date +%Y) = "2019" && /sbin/shutdown now


              To run the job every year:



              0 20 31 8 * /sbin/shutdown now





              share|improve this answer

































                -4
















                There may be an option to input the year to the shutdown command, but cron can be used to run commands only once at a specific point in time. For your example, try



                0 0 31 8 ? 2019  shutdown


                Beware: the above is not standard cron syntax.






                share|improve this answer























                • 2





                  1. This doesn’t say 20:00 pm, it says midnight. 2. I have never seen a cronjob with SIX fields for the timing. What cron implementation are you referencing?

                  – Wildcard
                  May 27 at 1:25






                • 2





                  There isn't a year field in the crontab schedule

                  – Seamus
                  May 27 at 2:06













                • I realized afterwards this syntax is not "standard cron", so I agree, it should not be taken at face value. OP seems to imply there is a performance penalty associated with using cron, so in my Answer, I sought to clarify - there isn't any inherently inefficient about cron's implementation that makes unsuitable for one-off task. Is this what you think as well?

                  – flow2k
                  May 29 at 7:43













                Your Answer








                StackExchange.ready(function() {
                var channelOptions = {
                tags: "".split(" "),
                id: "106"
                };
                initTagRenderer("".split(" "), "".split(" "), channelOptions);

                StackExchange.using("externalEditor", function() {
                // Have to fire editor after snippets, if snippets enabled
                if (StackExchange.settings.snippets.snippetsEnabled) {
                StackExchange.using("snippets", function() {
                createEditor();
                });
                }
                else {
                createEditor();
                }
                });

                function createEditor() {
                StackExchange.prepareEditor({
                heartbeatType: 'answer',
                autoActivateHeartbeat: false,
                convertImagesToLinks: false,
                noModals: true,
                showLowRepImageUploadWarning: true,
                reputationToPostImages: null,
                bindNavPrevention: true,
                postfix: "",
                imageUploader: {
                brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
                contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/4.0/"u003ecc by-sa 4.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
                allowUrls: true
                },
                onDemand: true,
                discardSelector: ".discard-answer"
                ,immediatelyShowMarkdownHelp:true
                });


                }
                });















                draft saved

                draft discarded
















                StackExchange.ready(
                function () {
                StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f521201%2fshutdown-at-specific-date%23new-answer', 'question_page');
                }
                );

                Post as a guest















                Required, but never shown

























                6 Answers
                6






                active

                oldest

                votes








                6 Answers
                6






                active

                oldest

                votes









                active

                oldest

                votes






                active

                oldest

                votes









                6
















                Recent Ubuntu versions use systemd and when the conventional atd and associated at scheduler for one-off commands is either not installed or not running a one-off command can be scheduled with systemd-run which is somewhat easier than manually generating a systemd timer:



                 systemd-run --on-calendar="2019-08-31 20:00:00 CET" /sbin/shutdown now





                share|improve this answer





















                • 2





                  The irony is that starting an entire service to do this is almost superfluous. systemd's shutdown mechanism itself supports arbitrary points in time. Its command-line tool simply does not provide the ability to access this, because it is not up to par with the command line of the BSD shutdown. As I wrote in another answer, you who want this could try persuading the systemd people to make their shutdown tool more capable, with syntax of decades' standing, rather than going around the houses with systemd-run.

                  – JdeBP
                  May 28 at 7:11













                • I get Invalid calendar spec: 2019-08-31 20:00:00 CET

                  – HdM Upload
                  Jun 2 at 14:44
















                6
















                Recent Ubuntu versions use systemd and when the conventional atd and associated at scheduler for one-off commands is either not installed or not running a one-off command can be scheduled with systemd-run which is somewhat easier than manually generating a systemd timer:



                 systemd-run --on-calendar="2019-08-31 20:00:00 CET" /sbin/shutdown now





                share|improve this answer





















                • 2





                  The irony is that starting an entire service to do this is almost superfluous. systemd's shutdown mechanism itself supports arbitrary points in time. Its command-line tool simply does not provide the ability to access this, because it is not up to par with the command line of the BSD shutdown. As I wrote in another answer, you who want this could try persuading the systemd people to make their shutdown tool more capable, with syntax of decades' standing, rather than going around the houses with systemd-run.

                  – JdeBP
                  May 28 at 7:11













                • I get Invalid calendar spec: 2019-08-31 20:00:00 CET

                  – HdM Upload
                  Jun 2 at 14:44














                6














                6










                6









                Recent Ubuntu versions use systemd and when the conventional atd and associated at scheduler for one-off commands is either not installed or not running a one-off command can be scheduled with systemd-run which is somewhat easier than manually generating a systemd timer:



                 systemd-run --on-calendar="2019-08-31 20:00:00 CET" /sbin/shutdown now





                share|improve this answer













                Recent Ubuntu versions use systemd and when the conventional atd and associated at scheduler for one-off commands is either not installed or not running a one-off command can be scheduled with systemd-run which is somewhat easier than manually generating a systemd timer:



                 systemd-run --on-calendar="2019-08-31 20:00:00 CET" /sbin/shutdown now






                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered May 27 at 11:48









                HBruijnHBruijn

                5,99316 silver badges28 bronze badges




                5,99316 silver badges28 bronze badges











                • 2





                  The irony is that starting an entire service to do this is almost superfluous. systemd's shutdown mechanism itself supports arbitrary points in time. Its command-line tool simply does not provide the ability to access this, because it is not up to par with the command line of the BSD shutdown. As I wrote in another answer, you who want this could try persuading the systemd people to make their shutdown tool more capable, with syntax of decades' standing, rather than going around the houses with systemd-run.

                  – JdeBP
                  May 28 at 7:11













                • I get Invalid calendar spec: 2019-08-31 20:00:00 CET

                  – HdM Upload
                  Jun 2 at 14:44














                • 2





                  The irony is that starting an entire service to do this is almost superfluous. systemd's shutdown mechanism itself supports arbitrary points in time. Its command-line tool simply does not provide the ability to access this, because it is not up to par with the command line of the BSD shutdown. As I wrote in another answer, you who want this could try persuading the systemd people to make their shutdown tool more capable, with syntax of decades' standing, rather than going around the houses with systemd-run.

                  – JdeBP
                  May 28 at 7:11













                • I get Invalid calendar spec: 2019-08-31 20:00:00 CET

                  – HdM Upload
                  Jun 2 at 14:44








                2




                2





                The irony is that starting an entire service to do this is almost superfluous. systemd's shutdown mechanism itself supports arbitrary points in time. Its command-line tool simply does not provide the ability to access this, because it is not up to par with the command line of the BSD shutdown. As I wrote in another answer, you who want this could try persuading the systemd people to make their shutdown tool more capable, with syntax of decades' standing, rather than going around the houses with systemd-run.

                – JdeBP
                May 28 at 7:11







                The irony is that starting an entire service to do this is almost superfluous. systemd's shutdown mechanism itself supports arbitrary points in time. Its command-line tool simply does not provide the ability to access this, because it is not up to par with the command line of the BSD shutdown. As I wrote in another answer, you who want this could try persuading the systemd people to make their shutdown tool more capable, with syntax of decades' standing, rather than going around the houses with systemd-run.

                – JdeBP
                May 28 at 7:11















                I get Invalid calendar spec: 2019-08-31 20:00:00 CET

                – HdM Upload
                Jun 2 at 14:44





                I get Invalid calendar spec: 2019-08-31 20:00:00 CET

                – HdM Upload
                Jun 2 at 14:44













                12
















                The at command is for scheduling one off future executions.



                e.g.



                % at 8pm Aug 31
                at> echo hello
                at> <EOT>
                job 161 at Sat Aug 31 20:00:00 2019


                (the "<EOT>" was produced by pressing control-D)



                % atq
                161 Sat Aug 31 20:00:00 2019 a sweh


                You can put your shutdown command here.






                share|improve this answer


























                • Yes! I had forgotten about at when I posted - at is definitely meant for this in general, although in a company the accepted method may be at or cron, depending on conventions related to configuration management/deployment.

                  – flow2k
                  May 27 at 4:57











                • It is not exactly equivalent, note. unix.stackexchange.com/q/465322/5132

                  – JdeBP
                  May 27 at 8:15











                • at is also able to take commands from a pipe: echo "echo yup > $(tty)" | at now.

                  – mosvy
                  May 27 at 23:19
















                12
















                The at command is for scheduling one off future executions.



                e.g.



                % at 8pm Aug 31
                at> echo hello
                at> <EOT>
                job 161 at Sat Aug 31 20:00:00 2019


                (the "<EOT>" was produced by pressing control-D)



                % atq
                161 Sat Aug 31 20:00:00 2019 a sweh


                You can put your shutdown command here.






                share|improve this answer


























                • Yes! I had forgotten about at when I posted - at is definitely meant for this in general, although in a company the accepted method may be at or cron, depending on conventions related to configuration management/deployment.

                  – flow2k
                  May 27 at 4:57











                • It is not exactly equivalent, note. unix.stackexchange.com/q/465322/5132

                  – JdeBP
                  May 27 at 8:15











                • at is also able to take commands from a pipe: echo "echo yup > $(tty)" | at now.

                  – mosvy
                  May 27 at 23:19














                12














                12










                12









                The at command is for scheduling one off future executions.



                e.g.



                % at 8pm Aug 31
                at> echo hello
                at> <EOT>
                job 161 at Sat Aug 31 20:00:00 2019


                (the "<EOT>" was produced by pressing control-D)



                % atq
                161 Sat Aug 31 20:00:00 2019 a sweh


                You can put your shutdown command here.






                share|improve this answer













                The at command is for scheduling one off future executions.



                e.g.



                % at 8pm Aug 31
                at> echo hello
                at> <EOT>
                job 161 at Sat Aug 31 20:00:00 2019


                (the "<EOT>" was produced by pressing control-D)



                % atq
                161 Sat Aug 31 20:00:00 2019 a sweh


                You can put your shutdown command here.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered May 26 at 23:25









                Stephen HarrisStephen Harris

                29.3k3 gold badges57 silver badges85 bronze badges




                29.3k3 gold badges57 silver badges85 bronze badges
















                • Yes! I had forgotten about at when I posted - at is definitely meant for this in general, although in a company the accepted method may be at or cron, depending on conventions related to configuration management/deployment.

                  – flow2k
                  May 27 at 4:57











                • It is not exactly equivalent, note. unix.stackexchange.com/q/465322/5132

                  – JdeBP
                  May 27 at 8:15











                • at is also able to take commands from a pipe: echo "echo yup > $(tty)" | at now.

                  – mosvy
                  May 27 at 23:19



















                • Yes! I had forgotten about at when I posted - at is definitely meant for this in general, although in a company the accepted method may be at or cron, depending on conventions related to configuration management/deployment.

                  – flow2k
                  May 27 at 4:57











                • It is not exactly equivalent, note. unix.stackexchange.com/q/465322/5132

                  – JdeBP
                  May 27 at 8:15











                • at is also able to take commands from a pipe: echo "echo yup > $(tty)" | at now.

                  – mosvy
                  May 27 at 23:19

















                Yes! I had forgotten about at when I posted - at is definitely meant for this in general, although in a company the accepted method may be at or cron, depending on conventions related to configuration management/deployment.

                – flow2k
                May 27 at 4:57





                Yes! I had forgotten about at when I posted - at is definitely meant for this in general, although in a company the accepted method may be at or cron, depending on conventions related to configuration management/deployment.

                – flow2k
                May 27 at 4:57













                It is not exactly equivalent, note. unix.stackexchange.com/q/465322/5132

                – JdeBP
                May 27 at 8:15





                It is not exactly equivalent, note. unix.stackexchange.com/q/465322/5132

                – JdeBP
                May 27 at 8:15













                at is also able to take commands from a pipe: echo "echo yup > $(tty)" | at now.

                – mosvy
                May 27 at 23:19





                at is also able to take commands from a pipe: echo "echo yup > $(tty)" | at now.

                – mosvy
                May 27 at 23:19











                7
















                While at is the obvious way to do this, I think it will survive shutdowns, so if the machine reboots before the scheduled shutdown, it might shutdown again at the scheduled time. Therefore, using bash and GNU date we can use a delayed shutdown.



                /sbin/shutdown +$(( ( $( date -d "30 may 2019 13:15" +%s ) - $( date +%s ) ) / 60 + 1 ))



                NB: This is only accurate to one minute. It works by converting the scheduled time, and now to seconds since the UNIX epoch, calculating the difference, converting to minutes, and then using this as the delay to shutdown. It won't work correctly if the scheduled time is in the past.






                share|improve this answer






























                  7
















                  While at is the obvious way to do this, I think it will survive shutdowns, so if the machine reboots before the scheduled shutdown, it might shutdown again at the scheduled time. Therefore, using bash and GNU date we can use a delayed shutdown.



                  /sbin/shutdown +$(( ( $( date -d "30 may 2019 13:15" +%s ) - $( date +%s ) ) / 60 + 1 ))



                  NB: This is only accurate to one minute. It works by converting the scheduled time, and now to seconds since the UNIX epoch, calculating the difference, converting to minutes, and then using this as the delay to shutdown. It won't work correctly if the scheduled time is in the past.






                  share|improve this answer




























                    7














                    7










                    7









                    While at is the obvious way to do this, I think it will survive shutdowns, so if the machine reboots before the scheduled shutdown, it might shutdown again at the scheduled time. Therefore, using bash and GNU date we can use a delayed shutdown.



                    /sbin/shutdown +$(( ( $( date -d "30 may 2019 13:15" +%s ) - $( date +%s ) ) / 60 + 1 ))



                    NB: This is only accurate to one minute. It works by converting the scheduled time, and now to seconds since the UNIX epoch, calculating the difference, converting to minutes, and then using this as the delay to shutdown. It won't work correctly if the scheduled time is in the past.






                    share|improve this answer













                    While at is the obvious way to do this, I think it will survive shutdowns, so if the machine reboots before the scheduled shutdown, it might shutdown again at the scheduled time. Therefore, using bash and GNU date we can use a delayed shutdown.



                    /sbin/shutdown +$(( ( $( date -d "30 may 2019 13:15" +%s ) - $( date +%s ) ) / 60 + 1 ))



                    NB: This is only accurate to one minute. It works by converting the scheduled time, and now to seconds since the UNIX epoch, calculating the difference, converting to minutes, and then using this as the delay to shutdown. It won't work correctly if the scheduled time is in the past.







                    share|improve this answer












                    share|improve this answer



                    share|improve this answer










                    answered May 27 at 10:54









                    CSMCSM

                    1,1626 silver badges4 bronze badges




                    1,1626 silver badges4 bronze badges


























                        3
















                        You use a better shutdown command.



                        The van Smoorenburg, Upstart, and systemd shutdown commands do not allow a date specification. But the BSD shutdown command takes a date value in its specification of when to shut down, in the form yymmddhhmm. This has been the case ever since 4BSD, and remains so with FreeBSD and OpenBSD. NetBSD extended it to ccyymmddhhmm.



                        Because the nosh toolset is also usable on the BSDs, I gave my shutdown command the same capability, extending it to CCYYMMDDHHMM per NetBSD. And because the nosh toolset is also usable on Linux, that gives Linux a shutdown command that takes dates.



                        It of course works with the nosh system-manager. It also works with some other systems. It sends signals to process #1 to enact stuff and the same signals are understood by some other system managers, such as systemd, which can also be shut down using it.



                        You could use it, or a tool like it; or you could try to persuade the authors of other Linux shutdown programs to extend their tools to also be as capable as the BSD shutdown.



                        Further reading




                        • Jonathan de Boyne Pollard (2018). shutdown. nosh toolset manual pages. Softwares.

                        • Jonathan de Boyne Pollard (2018). system-manager. nosh toolset manual pages. Softwares.


                        • shutdown. System Manager's Manual. NetBSD Manual pages. 2011-11-04.


                        • shutdown. FreeBSD System Managers' Manual. 2018-01-01.


                        • shutdown. OpenBSD Manual pages. 2015-01-21.

                        • https://unix.stackexchange.com/a/465337/5132






                        share|improve this answer






























                          3
















                          You use a better shutdown command.



                          The van Smoorenburg, Upstart, and systemd shutdown commands do not allow a date specification. But the BSD shutdown command takes a date value in its specification of when to shut down, in the form yymmddhhmm. This has been the case ever since 4BSD, and remains so with FreeBSD and OpenBSD. NetBSD extended it to ccyymmddhhmm.



                          Because the nosh toolset is also usable on the BSDs, I gave my shutdown command the same capability, extending it to CCYYMMDDHHMM per NetBSD. And because the nosh toolset is also usable on Linux, that gives Linux a shutdown command that takes dates.



                          It of course works with the nosh system-manager. It also works with some other systems. It sends signals to process #1 to enact stuff and the same signals are understood by some other system managers, such as systemd, which can also be shut down using it.



                          You could use it, or a tool like it; or you could try to persuade the authors of other Linux shutdown programs to extend their tools to also be as capable as the BSD shutdown.



                          Further reading




                          • Jonathan de Boyne Pollard (2018). shutdown. nosh toolset manual pages. Softwares.

                          • Jonathan de Boyne Pollard (2018). system-manager. nosh toolset manual pages. Softwares.


                          • shutdown. System Manager's Manual. NetBSD Manual pages. 2011-11-04.


                          • shutdown. FreeBSD System Managers' Manual. 2018-01-01.


                          • shutdown. OpenBSD Manual pages. 2015-01-21.

                          • https://unix.stackexchange.com/a/465337/5132






                          share|improve this answer




























                            3














                            3










                            3









                            You use a better shutdown command.



                            The van Smoorenburg, Upstart, and systemd shutdown commands do not allow a date specification. But the BSD shutdown command takes a date value in its specification of when to shut down, in the form yymmddhhmm. This has been the case ever since 4BSD, and remains so with FreeBSD and OpenBSD. NetBSD extended it to ccyymmddhhmm.



                            Because the nosh toolset is also usable on the BSDs, I gave my shutdown command the same capability, extending it to CCYYMMDDHHMM per NetBSD. And because the nosh toolset is also usable on Linux, that gives Linux a shutdown command that takes dates.



                            It of course works with the nosh system-manager. It also works with some other systems. It sends signals to process #1 to enact stuff and the same signals are understood by some other system managers, such as systemd, which can also be shut down using it.



                            You could use it, or a tool like it; or you could try to persuade the authors of other Linux shutdown programs to extend their tools to also be as capable as the BSD shutdown.



                            Further reading




                            • Jonathan de Boyne Pollard (2018). shutdown. nosh toolset manual pages. Softwares.

                            • Jonathan de Boyne Pollard (2018). system-manager. nosh toolset manual pages. Softwares.


                            • shutdown. System Manager's Manual. NetBSD Manual pages. 2011-11-04.


                            • shutdown. FreeBSD System Managers' Manual. 2018-01-01.


                            • shutdown. OpenBSD Manual pages. 2015-01-21.

                            • https://unix.stackexchange.com/a/465337/5132






                            share|improve this answer













                            You use a better shutdown command.



                            The van Smoorenburg, Upstart, and systemd shutdown commands do not allow a date specification. But the BSD shutdown command takes a date value in its specification of when to shut down, in the form yymmddhhmm. This has been the case ever since 4BSD, and remains so with FreeBSD and OpenBSD. NetBSD extended it to ccyymmddhhmm.



                            Because the nosh toolset is also usable on the BSDs, I gave my shutdown command the same capability, extending it to CCYYMMDDHHMM per NetBSD. And because the nosh toolset is also usable on Linux, that gives Linux a shutdown command that takes dates.



                            It of course works with the nosh system-manager. It also works with some other systems. It sends signals to process #1 to enact stuff and the same signals are understood by some other system managers, such as systemd, which can also be shut down using it.



                            You could use it, or a tool like it; or you could try to persuade the authors of other Linux shutdown programs to extend their tools to also be as capable as the BSD shutdown.



                            Further reading




                            • Jonathan de Boyne Pollard (2018). shutdown. nosh toolset manual pages. Softwares.

                            • Jonathan de Boyne Pollard (2018). system-manager. nosh toolset manual pages. Softwares.


                            • shutdown. System Manager's Manual. NetBSD Manual pages. 2011-11-04.


                            • shutdown. FreeBSD System Managers' Manual. 2018-01-01.


                            • shutdown. OpenBSD Manual pages. 2015-01-21.

                            • https://unix.stackexchange.com/a/465337/5132







                            share|improve this answer












                            share|improve this answer



                            share|improve this answer










                            answered May 27 at 9:11









                            JdeBPJdeBP

                            41.8k5 gold badges91 silver badges205 bronze badges




                            41.8k5 gold badges91 silver badges205 bronze badges


























                                1
















                                To run the job only this year:



                                0 20 31 8 * test $(/bin/date +%Y) = "2019" && /sbin/shutdown now


                                To run the job every year:



                                0 20 31 8 * /sbin/shutdown now





                                share|improve this answer






























                                  1
















                                  To run the job only this year:



                                  0 20 31 8 * test $(/bin/date +%Y) = "2019" && /sbin/shutdown now


                                  To run the job every year:



                                  0 20 31 8 * /sbin/shutdown now





                                  share|improve this answer




























                                    1














                                    1










                                    1









                                    To run the job only this year:



                                    0 20 31 8 * test $(/bin/date +%Y) = "2019" && /sbin/shutdown now


                                    To run the job every year:



                                    0 20 31 8 * /sbin/shutdown now





                                    share|improve this answer













                                    To run the job only this year:



                                    0 20 31 8 * test $(/bin/date +%Y) = "2019" && /sbin/shutdown now


                                    To run the job every year:



                                    0 20 31 8 * /sbin/shutdown now






                                    share|improve this answer












                                    share|improve this answer



                                    share|improve this answer










                                    answered May 26 at 23:58









                                    FreddyFreddy

                                    8,2731 gold badge6 silver badges29 bronze badges




                                    8,2731 gold badge6 silver badges29 bronze badges


























                                        -4
















                                        There may be an option to input the year to the shutdown command, but cron can be used to run commands only once at a specific point in time. For your example, try



                                        0 0 31 8 ? 2019  shutdown


                                        Beware: the above is not standard cron syntax.






                                        share|improve this answer























                                        • 2





                                          1. This doesn’t say 20:00 pm, it says midnight. 2. I have never seen a cronjob with SIX fields for the timing. What cron implementation are you referencing?

                                          – Wildcard
                                          May 27 at 1:25






                                        • 2





                                          There isn't a year field in the crontab schedule

                                          – Seamus
                                          May 27 at 2:06













                                        • I realized afterwards this syntax is not "standard cron", so I agree, it should not be taken at face value. OP seems to imply there is a performance penalty associated with using cron, so in my Answer, I sought to clarify - there isn't any inherently inefficient about cron's implementation that makes unsuitable for one-off task. Is this what you think as well?

                                          – flow2k
                                          May 29 at 7:43
















                                        -4
















                                        There may be an option to input the year to the shutdown command, but cron can be used to run commands only once at a specific point in time. For your example, try



                                        0 0 31 8 ? 2019  shutdown


                                        Beware: the above is not standard cron syntax.






                                        share|improve this answer























                                        • 2





                                          1. This doesn’t say 20:00 pm, it says midnight. 2. I have never seen a cronjob with SIX fields for the timing. What cron implementation are you referencing?

                                          – Wildcard
                                          May 27 at 1:25






                                        • 2





                                          There isn't a year field in the crontab schedule

                                          – Seamus
                                          May 27 at 2:06













                                        • I realized afterwards this syntax is not "standard cron", so I agree, it should not be taken at face value. OP seems to imply there is a performance penalty associated with using cron, so in my Answer, I sought to clarify - there isn't any inherently inefficient about cron's implementation that makes unsuitable for one-off task. Is this what you think as well?

                                          – flow2k
                                          May 29 at 7:43














                                        -4














                                        -4










                                        -4









                                        There may be an option to input the year to the shutdown command, but cron can be used to run commands only once at a specific point in time. For your example, try



                                        0 0 31 8 ? 2019  shutdown


                                        Beware: the above is not standard cron syntax.






                                        share|improve this answer















                                        There may be an option to input the year to the shutdown command, but cron can be used to run commands only once at a specific point in time. For your example, try



                                        0 0 31 8 ? 2019  shutdown


                                        Beware: the above is not standard cron syntax.







                                        share|improve this answer














                                        share|improve this answer



                                        share|improve this answer








                                        edited May 29 at 7:43

























                                        answered May 26 at 23:01









                                        flow2kflow2k

                                        2492 silver badges14 bronze badges




                                        2492 silver badges14 bronze badges











                                        • 2





                                          1. This doesn’t say 20:00 pm, it says midnight. 2. I have never seen a cronjob with SIX fields for the timing. What cron implementation are you referencing?

                                          – Wildcard
                                          May 27 at 1:25






                                        • 2





                                          There isn't a year field in the crontab schedule

                                          – Seamus
                                          May 27 at 2:06













                                        • I realized afterwards this syntax is not "standard cron", so I agree, it should not be taken at face value. OP seems to imply there is a performance penalty associated with using cron, so in my Answer, I sought to clarify - there isn't any inherently inefficient about cron's implementation that makes unsuitable for one-off task. Is this what you think as well?

                                          – flow2k
                                          May 29 at 7:43














                                        • 2





                                          1. This doesn’t say 20:00 pm, it says midnight. 2. I have never seen a cronjob with SIX fields for the timing. What cron implementation are you referencing?

                                          – Wildcard
                                          May 27 at 1:25






                                        • 2





                                          There isn't a year field in the crontab schedule

                                          – Seamus
                                          May 27 at 2:06













                                        • I realized afterwards this syntax is not "standard cron", so I agree, it should not be taken at face value. OP seems to imply there is a performance penalty associated with using cron, so in my Answer, I sought to clarify - there isn't any inherently inefficient about cron's implementation that makes unsuitable for one-off task. Is this what you think as well?

                                          – flow2k
                                          May 29 at 7:43








                                        2




                                        2





                                        1. This doesn’t say 20:00 pm, it says midnight. 2. I have never seen a cronjob with SIX fields for the timing. What cron implementation are you referencing?

                                        – Wildcard
                                        May 27 at 1:25





                                        1. This doesn’t say 20:00 pm, it says midnight. 2. I have never seen a cronjob with SIX fields for the timing. What cron implementation are you referencing?

                                        – Wildcard
                                        May 27 at 1:25




                                        2




                                        2





                                        There isn't a year field in the crontab schedule

                                        – Seamus
                                        May 27 at 2:06







                                        There isn't a year field in the crontab schedule

                                        – Seamus
                                        May 27 at 2:06















                                        I realized afterwards this syntax is not "standard cron", so I agree, it should not be taken at face value. OP seems to imply there is a performance penalty associated with using cron, so in my Answer, I sought to clarify - there isn't any inherently inefficient about cron's implementation that makes unsuitable for one-off task. Is this what you think as well?

                                        – flow2k
                                        May 29 at 7:43





                                        I realized afterwards this syntax is not "standard cron", so I agree, it should not be taken at face value. OP seems to imply there is a performance penalty associated with using cron, so in my Answer, I sought to clarify - there isn't any inherently inefficient about cron's implementation that makes unsuitable for one-off task. Is this what you think as well?

                                        – flow2k
                                        May 29 at 7:43



















                                        draft saved

                                        draft discarded



















































                                        Thanks for contributing an answer to Unix & Linux Stack Exchange!


                                        • Please be sure to answer the question. Provide details and share your research!

                                        But avoid



                                        • Asking for help, clarification, or responding to other answers.

                                        • Making statements based on opinion; back them up with references or personal experience.


                                        To learn more, see our tips on writing great answers.




                                        draft saved


                                        draft discarded














                                        StackExchange.ready(
                                        function () {
                                        StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f521201%2fshutdown-at-specific-date%23new-answer', 'question_page');
                                        }
                                        );

                                        Post as a guest















                                        Required, but never shown





















































                                        Required, but never shown














                                        Required, but never shown












                                        Required, but never shown







                                        Required, but never shown

































                                        Required, but never shown














                                        Required, but never shown












                                        Required, but never shown







                                        Required, but never shown







                                        Popular posts from this blog

                                        Færeyskur hestur Heimild | Tengill | Tilvísanir | LeiðsagnarvalRossið - síða um færeyska hrossið á færeyskuGott ár hjá færeyska hestinum

                                        He _____ here since 1970 . Answer needed [closed]What does “since he was so high” mean?Meaning of “catch birds for”?How do I ensure “since” takes the meaning I want?“Who cares here” meaningWhat does “right round toward” mean?the time tense (had now been detected)What does the phrase “ring around the roses” mean here?Correct usage of “visited upon”Meaning of “foiled rail sabotage bid”It was the third time I had gone to Rome or It is the third time I had been to Rome

                                        Slayer Innehåll Historia | Stil, komposition och lyrik | Bandets betydelse och framgångar | Sidoprojekt och samarbeten | Kontroverser | Medlemmar | Utmärkelser och nomineringar | Turnéer och festivaler | Diskografi | Referenser | Externa länkar | Navigeringsmenywww.slayer.net”Metal Massacre vol. 1””Metal Massacre vol. 3””Metal Massacre Volume III””Show No Mercy””Haunting the Chapel””Live Undead””Hell Awaits””Reign in Blood””Reign in Blood””Gold & Platinum – Reign in Blood””Golden Gods Awards Winners”originalet”Kerrang! Hall Of Fame””Slayer Looks Back On 37-Year Career In New Video Series: Part Two””South of Heaven””Gold & Platinum – South of Heaven””Seasons in the Abyss””Gold & Platinum - Seasons in the Abyss””Divine Intervention””Divine Intervention - Release group by Slayer””Gold & Platinum - Divine Intervention””Live Intrusion””Undisputed Attitude””Abolish Government/Superficial Love””Release “Slatanic Slaughter: A Tribute to Slayer” by Various Artists””Diabolus in Musica””Soundtrack to the Apocalypse””God Hates Us All””Systematic - Relationships””War at the Warfield””Gold & Platinum - War at the Warfield””Soundtrack to the Apocalypse””Gold & Platinum - Still Reigning””Metallica, Slayer, Iron Mauden Among Winners At Metal Hammer Awards””Eternal Pyre””Eternal Pyre - Slayer release group””Eternal Pyre””Metal Storm Awards 2006””Kerrang! Hall Of Fame””Slayer Wins 'Best Metal' Grammy Award””Slayer Guitarist Jeff Hanneman Dies””Bullet-For My Valentine booed at Metal Hammer Golden Gods Awards””Unholy Aliance””The End Of Slayer?””Slayer: We Could Thrash Out Two More Albums If We're Fast Enough...””'The Unholy Alliance: Chapter III' UK Dates Added”originalet”Megadeth And Slayer To Co-Headline 'Canadian Carnage' Trek”originalet”World Painted Blood””Release “World Painted Blood” by Slayer””Metallica Heading To Cinemas””Slayer, Megadeth To Join Forces For 'European Carnage' Tour - Dec. 18, 2010”originalet”Slayer's Hanneman Contracts Acute Infection; Band To Bring In Guest Guitarist””Cannibal Corpse's Pat O'Brien Will Step In As Slayer's Guest Guitarist”originalet”Slayer’s Jeff Hanneman Dead at 49””Dave Lombardo Says He Made Only $67,000 In 2011 While Touring With Slayer””Slayer: We Do Not Agree With Dave Lombardo's Substance Or Timeline Of Events””Slayer Welcomes Drummer Paul Bostaph Back To The Fold””Slayer Hope to Unveil Never-Before-Heard Jeff Hanneman Material on Next Album””Slayer Debut New Song 'Implode' During Surprise Golden Gods Appearance””Release group Repentless by Slayer””Repentless - Slayer - Credits””Slayer””Metal Storm Awards 2015””Slayer - to release comic book "Repentless #1"””Slayer To Release 'Repentless' 6.66" Vinyl Box Set””BREAKING NEWS: Slayer Announce Farewell Tour””Slayer Recruit Lamb of God, Anthrax, Behemoth + Testament for Final Tour””Slayer lägger ner efter 37 år””Slayer Announces Second North American Leg Of 'Final' Tour””Final World Tour””Slayer Announces Final European Tour With Lamb of God, Anthrax And Obituary””Slayer To Tour Europe With Lamb of God, Anthrax And Obituary””Slayer To Play 'Last French Show Ever' At Next Year's Hellfst””Slayer's Final World Tour Will Extend Into 2019””Death Angel's Rob Cavestany On Slayer's 'Farewell' Tour: 'Some Of Us Could See This Coming'””Testament Has No Plans To Retire Anytime Soon, Says Chuck Billy””Anthrax's Scott Ian On Slayer's 'Farewell' Tour Plans: 'I Was Surprised And I Wasn't Surprised'””Slayer””Slayer's Morbid Schlock””Review/Rock; For Slayer, the Mania Is the Message””Slayer - Biography””Slayer - Reign In Blood”originalet”Dave Lombardo””An exclusive oral history of Slayer”originalet”Exclusive! Interview With Slayer Guitarist Jeff Hanneman”originalet”Thinking Out Loud: Slayer's Kerry King on hair metal, Satan and being polite””Slayer Lyrics””Slayer - Biography””Most influential artists for extreme metal music””Slayer - Reign in Blood””Slayer guitarist Jeff Hanneman dies aged 49””Slatanic Slaughter: A Tribute to Slayer””Gateway to Hell: A Tribute to Slayer””Covered In Blood””Slayer: The Origins of Thrash in San Francisco, CA.””Why They Rule - #6 Slayer”originalet”Guitar World's 100 Greatest Heavy Metal Guitarists Of All Time”originalet”The fans have spoken: Slayer comes out on top in readers' polls”originalet”Tribute to Jeff Hanneman (1964-2013)””Lamb Of God Frontman: We Sound Like A Slayer Rip-Off””BEHEMOTH Frontman Pays Tribute To SLAYER's JEFF HANNEMAN””Slayer, Hatebreed Doing Double Duty On This Year's Ozzfest””System of a Down””Lacuna Coil’s Andrea Ferro Talks Influences, Skateboarding, Band Origins + More””Slayer - Reign in Blood””Into The Lungs of Hell””Slayer rules - en utställning om fans””Slayer and Their Fans Slashed Through a No-Holds-Barred Night at Gas Monkey””Home””Slayer””Gold & Platinum - The Big 4 Live from Sofia, Bulgaria””Exclusive! Interview With Slayer Guitarist Kerry King””2008-02-23: Wiltern, Los Angeles, CA, USA””Slayer's Kerry King To Perform With Megadeth Tonight! - Oct. 21, 2010”originalet”Dave Lombardo - Biography”Slayer Case DismissedArkiveradUltimate Classic Rock: Slayer guitarist Jeff Hanneman dead at 49.”Slayer: "We could never do any thing like Some Kind Of Monster..."””Cannibal Corpse'S Pat O'Brien Will Step In As Slayer'S Guest Guitarist | The Official Slayer Site”originalet”Slayer Wins 'Best Metal' Grammy Award””Slayer Guitarist Jeff Hanneman Dies””Kerrang! Awards 2006 Blog: Kerrang! Hall Of Fame””Kerrang! Awards 2013: Kerrang! Legend”originalet”Metallica, Slayer, Iron Maien Among Winners At Metal Hammer Awards””Metal Hammer Golden Gods Awards””Bullet For My Valentine Booed At Metal Hammer Golden Gods Awards””Metal Storm Awards 2006””Metal Storm Awards 2015””Slayer's Concert History””Slayer - Relationships””Slayer - Releases”Slayers officiella webbplatsSlayer på MusicBrainzOfficiell webbplatsSlayerSlayerr1373445760000 0001 1540 47353068615-5086262726cb13906545x(data)6033143kn20030215029