Ubuntu-fr

Madjai-2

Commande shutdown ne met pas hors-tension la machine

Bonjour.

Je cherche à réaliser un script permettant d'éteindre à heure fixe mon pc. Après plusieurs recherches sur le net, j'ai trouvé et réussi à réaliser le script, à le faire démarré au boot. Cependant, quoi que je fasse, mon pc reste bloqué sur l'écran de fermeture d'Ubuntu, avec le logo et les points dessous qui passent du blanc au orange et inversement.

le script en question, tout simple :

#!/bin/bash
sudo shutdown -h temps

Le souci est donc que le pc ne s'éteint pas, même en laissant tourner une heure. J'ai cherché du côté de la commande shutdown, mais même en variant les options (-p, -H, etc), il n'y a aucun changement.

Pourriez-vous me dire ce qui ne va pas ? Est-ce un problème connu, un bug ? Comment y remédier ?

BrunoGey

Re : Commande shutdown ne met pas hors-tension la machine

Bonjour,

les explications sont dans le man shutdown :

shutdown(8)                                                        shutdown(8)

NAME
       shutdown - bring the system down

SYNOPSIS
       shutdown [OPTION]...  TIME [MESSAGE]

DESCRIPTION
       shutdown arranges for the system to be brought down in a safe way.  All
       logged-in users are notified that the system is going down and,  within
       the last five minutes of TIME, new logins are prevented.

       TIME  may  have  different  formats, the most common is simply the word
       'now' which will bring the system down immediately.  Other  valid  for‐
       mats  are  +m,  where m is the number of minutes to wait until shutting
       down and hh:mm which specifies the time on the 24hr clock.

       Once TIME has elapsed, shutdown sends a request to the  init(8)  daemon
       to bring the system down into the appropriate runlevel.

       This is performed by emitting the runlevel(7) event, which includes the
       new runlevel in the RUNLEVEL environment variable as well as the previ‐
       ous  runlevel  (obtained from the environment or from /var/run/utmp) in
       the PREVLEVEL variable.  An additional INIT_HALT variable may  be  set,
       this will contain the value HALT when bringing the system down for halt
       and POWEROFF when bringing the system down for power off.

OPTIONS
       -r     Requests that the system be rebooted after it has  been  brought
              down.

       -h     Requests  that  the system be either halted or powered off after
              it has been brought down, with the choice as to which left up to
              the system.

       -H     Requests  that  the  system  be halted after it has been brought
              down.
       -P     Requests that the system  be  powered  off  after  it  has  been
              brought down.

       -c     Cancels  a  running  shutdown.   TIME is not specified with this
              option, the first argument is MESSAGE.

       -k     Only send out the warning messages and disable  logins,  do  not
              actually bring the system down.

ENVIRONMENT
       RUNLEVEL
              shutdown  will  read  the current runlevel from this environment
              variable if set in preference to reading from /var/run/utmp

FILES
       /var/run/utmp
              Where the current runlevel will be read  from;  this  file  will
              also be updated with the new runlevel.

       /var/log/wtmp
              A  new runlevel record will be appended to this file for the new
              runlevel.

NOTES
       The Upstart init(8) daemon does not keep  track  of  runlevels  itself,
       instead they are implemented entirely by its userspace tools.

       See runlevel(7) for more details.

AUTHOR
       Written by Scott James Remnant <scott@netsplit.com>

REPORTING BUGS
       Report bugs at <https://launchpad.net/upstart/+bugs>

COPYRIGHT
       Copyright © 2009 Canonical Ltd.
       This is free software; see the source for copying conditions.  There is
       NO warranty; not even for MERCHANTABILITY or FITNESS FOR  A  PARTICULAR
       PURPOSE.

SEE ALSO
       runlevel(7) init(8) telinit(8) reboot(8)

it te faut l'executer en root "sudo shutdown" et mettre un paramètre de temps (valeur numerique en secondes )
genre sudo shutdown 5 pour 5secondes, et "sudo shutdown now" pour arret immédiat
il te faudra gérer le mdp admin en paramètre
-> "sudo shutdown now admin", non désolé ne marche pas

et pour l'executer à une heure précise tous les jours, c'est une tache "at" :

man "at" donne :

AT(1)                                                                    AT(1)

NAME
       at,  batch,  atq, atrm - queue, examine or delete jobs for later execu‐
       tion

SYNOPSIS
       at [-V] [-q queue] [-f file] [-mMlv] timespec...
       at [-V] [-q queue] [-f file] [-mMkv] [-t time]
       at -c job [job...]
       atq [-V] [-q queue]
       at [-rd] job [job...]
       atrm [-V] job [job...]
       batch
       at -b

DESCRIPTION
       at and batch read commands from standard  input  or  a  specified  file
       which are to be executed at a later time, using /bin/sh.

       at      executes commands at a specified time.

       atq     lists  the  user's  pending  jobs, unless the user is the supe‐
               ruser; in that case, everybody's jobs are listed.   The  format
               of  the  output  lines (one for each job) is: Job number, date,
               hour, queue, and username.

       atrm    deletes jobs, identified by their job number.

       batch   executes commands when system  load  levels  permit;  in  other
               words,  when  the  load  average  drops below 1.5, or the value
               specified in the invocation of atd.

       At allows fairly complex time  specifications,  extending  the  POSIX.2
       standard.   It  accepts  times of the form HH:MM to run a job at a spe‐
       cific time of day.  (If that time is already  past,  the  next  day  is
       assumed.)   You  may  also specify midnight, noon, or teatime (4pm) and
       you can have a time-of-day suffixed with AM or PM for  running  in  the
       morning or the evening.  You can also say what day the job will be run,
       by giving a date in the form month-name day with an optional  year,  or
       giving  a  date  of  the form MMDD[CC]YY, MM/DD/[CC]YY, DD.MM.[CC]YY or
       [CC]YY-MM-DD.  The specification of a date must follow  the  specifica‐
       tion  of  the  time  of  day.  You can also give times like now + count
       time-units, where the time-units can be minutes, hours, days, or  weeks
       and  you  can  tell  at to run the job today by suffixing the time with
       today and to run the job tomorrow by suffixing the time with tomorrow.

       For example, to run a job at 4pm three days from now, you would  do  at
       4pm  + 3 days, to run a job at 10:00am on July 31, you would do at 10am
       Jul 31 and to run a job at 1am tomorrow, you would do at 1am tomorrow.

       The  definition  of  the   time   specification   can   be   found   in
       /usr/share/doc/at/timespec.

       For  both  at  and  batch, commands are read from standard input or the
       file specified with the -f option and executed.  The working directory,
       the environment (except for the variables BASH_VERSINFO, DISPLAY, EUID,
       GROUPS, SHELLOPTS, TERM, UID, and _) and the umask  are  retained  from
       the time of invocation.

       As  at  is currently implemented as a setuid program, other environment
       variables (e.g.  LD_LIBRARY_PATH or LD_PRELOAD) are also not  exported.
       This  may  change  in the future.  As a workaround, set these variables
       explicitly in your job.

       An at - or batch - command invoked from a su(1) shell will  retain  the
       current  userid.   The  user will be mailed standard error and standard
       output from his commands, if any.  Mail will be sent using the  command
       /usr/sbin/sendmail.  If at is executed from a su(1) shell, the owner of
       the login shell will receive the mail.

       The superuser may use these commands in any  case.   For  other  users,
       permission  to  use  at  is  determined  by the files /etc/at.allow and
       /etc/at.deny.  See at.allow(5) for details.

OPTIONS
       -V      prints the version number to standard error and  exit  success‐
               fully.

       -q queue
               uses  the  specified  queue.  A queue designation consists of a
               single letter; valid queue designations range from a to z and A
               to  Z.   The  a queue is the default for at and the b queue for
               batch.  Queues with higher letters run with increased niceness.
               The  special queue "=" is reserved for jobs which are currently
               running.

       If a job is submitted to a queue designated with an  uppercase  letter,
       the  job is treated as if it were submitted to batch at the time of the
       job.  Once the time is reached, the batch processing rules with respect
       to  load average apply.  If atq is given a specific queue, it will only
       show jobs pending in that queue.

       -m      Send mail to the user when the job has completed even if  there
               was no output.

       -M      Never send mail to the user.

       -f file Reads the job from file rather than standard input.

       -t time run the job at time, given in the format [[CC]YY]MMDDhhmm[.ss]

       -l      Is an alias for atq.

       -r      Is an alias for atrm.

       -d      Is an alias for atrm.

       -b      is an alias for batch.

       -v      Shows the time the job will be executed before reading the job.

       Times displayed will be in the format "Thu Feb 20 14:50:00 1997".
       -c     cats the jobs listed on the command line to standard output.

FILES
       /var/spool/cron/atjobs
       /var/spool/cron/atspool
       /proc/loadavg
       /var/run/utmp
       /etc/at.allow
       /etc/at.deny

SEE ALSO
       at.allow(5), at.deny(5), atd(8), cron(1), nice(1), sh(1), umask(2).

BUGS
       The  correct  operation of batch for Linux depends on the presence of a
       proc- type directory mounted on /proc.

       If the file /var/run/utmp is not available or corrupted, or if the user
       is  not  logged  on  at the time at is invoked, the mail is sent to the
       userid found in the environment variable LOGNAME.  If that is undefined
       or empty, the current userid is assumed.

       At  and  batch as presently implemented are not suitable when users are
       competing for resources.  If this is the case for your site, you  might
       want to consider another batch system, such as nqs.

AUTHOR
       At was mostly written by Thomas Koenig, ig25@rz.uni-karlsruhe.de.

Dernière modification par BrunoGey (Le 29/05/2015, à 11:07)

---

Le PC Samsung R720,  Systeme : Ubuntu 16.04.1  noyau 4.4.0-145-generic #171
Session graphique : Standard Unity. Formattez vos posts avec les balises BBcode
Rigolo ;-)    Pebkac2.fr

Madjai-2

Re : Commande shutdown ne met pas hors-tension la machine

Sauf que ma question ne porte pas sur le script ou l'utilisation de man pour savoir ce que fait une commande et comment l'utiliser. Tout cela, je sais faire.

Ma question porte sur le fait que "shutdown" ferme la session, prépare le pc à l'extinction, mais qu'effectivement le pc reste bloqué sur l'écran Ubuntu de chargement sans s'éteindre.

"Poweroff" et "init 0" ou "telinit 0" font exactement pareil. Ce que je veux moi, c'est une mise hors-tension de ma machine après fermeture de l'OS. Là je n'ai que la fermeture de l'OS visiblement.

BrunoGey

Re : Commande shutdown ne met pas hors-tension la machine

Bonjour Mafdjal-2,

c'est bizarre ce que tu dis : tapes dans un terminal : "sudo shutdown now"
EDIT :

Bon j'ai trouvé : c'est "sudo shutdown -P now" ( P majuscule ), qui "éteind = poweroff", le pc
reste à gérer le mdp admin.
Et pour le faire tous les jours à l'heure dite, il va te falloir t'en sortir avec une tâche "cron"

normalement ça éteint le pc, pas "déconnexion" ni "mise en veille", bien "éteindre".

c'est pourquoi, j'ai cru bien faire en suggérant  un truc genre "at  time shutdown"
peut être est ce : " sudo at time shutdown now", reste à gérer le mdp admin en paramètre ?

cdt   

bruno

Dernière modification par BrunoGey (Le 30/05/2015, à 12:21)

---

Le PC Samsung R720,  Systeme : Ubuntu 16.04.1  noyau 4.4.0-145-generic #171
Session graphique : Standard Unity. Formattez vos posts avec les balises BBcode
Rigolo ;-)    Pebkac2.fr