web-dev-qa-db-fra.com

Surveiller le dossier et exécuter la commande s'il y a un fichier?

J'aimerais avoir mon moniteur Ubuntu Folder A. S'il y a un fichier .sh, j'aimerais le déplacer vers Folder B et l'exécuter en arrière-plan. Est-ce possible? Que devrais-je utiliser pour y arriver?

command-linebashscriptsdirectoryinotify
3
Ignacio

Vous avez quelques options:

1. Utiliser inotifywait

#!/bin/bash
# set path to watch
DIR="/path/to/sourcedir"
# set path to copy the script to
target_dir="/path/to/targetdir"

inotifywait -m -r -e moved_to -e create "$DIR" --format "%f" | while read f

do
    echo $f
    # check if the file is a .sh file
    if [[ $f = *.sh ]]; then
      # if so, copy the file to the target dir
      mv "$DIR/$f" "$target_dir"
      # and rum it
      /bin/bash "$target_dir/$f" &
    fi
done

Explication sur inotifywait

Définir les options

Pour vous connecter continuellement, vous devez définir l'option -m:

de man inotifywait:

-m, --monitor
    Instead of exiting after receiving a single event, execute indefinitely. The default behaviour is to exit after the first event occurs.

Pour vous connecter de manière récursive, vous devez définir l'option -r:

-r, --recursive
    Watch all subdirectories of any directories passed as arguments. Watches will be set up recursively to an unlimited depth. Symbolic links are not traversed. Newly created subdirectories will also be watched.

Si vous n'avez pas besoin de surveillance récursive, supprimez l'option.

événements

De plus, vous devez spécifier le (s) événement (s) pour déclencher:

EVENTS
       The following events are valid for use with the -e option:

       access A  watched  file  or  a file within a watched directory was read
              from.

       modify A watched file or a file within a watched directory was  written
              to.

       attrib The metadata of a watched file or a file within a watched direc‐
              tory was modified.  This includes timestamps, file  permissions,
              extended attributes etc.

       close_write
              A  watched file or a file within a watched directory was closed,
              after being opened in writeable mode.  This does not necessarily
              imply the file was written to.

       close_nowrite
              A  watched file or a file within a watched directory was closed,
              after being opened in read-only mode.

       close  A watched file or a file within a watched directory was  closed,
              regardless  of  how  it  was opened.  Note that this is actually
              implemented  simply  by  listening  for  both  close_write   and
              close_nowrite, hence all close events received will be output as
              one of these, not CLOSE.

       open   A watched file or a file within a watched directory was opened.

       moved_to
              A file or directory was moved into a  watched  directory.   This
              event  occurs  even  if the file is simply moved from and to the
              same directory.

       moved_from
              A file or directory was moved from a  watched  directory.   This
              event  occurs  even  if the file is simply moved from and to the
              same directory.

       move   A file or directory was moved from or to  a  watched  directory.
              Note  that  this is actually implemented simply by listening for
              both moved_to and moved_from, hence all  close  events  received
              will be output as one or both of these, not MOVE.

       move_self
              A  watched  file  or  directory was moved. After this event, the
              file or directory is no longer being watched.

       create A file or directory was created within a watched directory.

       delete A file or directory within a watched directory was deleted.

       delete_self
              A watched file or directory was deleted.  After this  event  the
              file  or  directory  is no longer being watched.  Note that this
              event can occur even if it is not explicitly being listened for.

       unmount
              The filesystem on which a watched file or directory resides  was
              unmounted.   After this event the file or directory is no longer
              being watched.  Note that this event can occur even if it is not
              explicitly being listened to.

Vous devez prévoir chaque événement à déclencher avec -e:

-e moved_to -e create

Vous pouvez bien sûr définir n'importe quel déclencheur d'événement de la liste.

Avec l’option --format "%f", nous donnons à la commande le nom du fichier , que nous utiliserons pour copier et exécuter le fichier, associé au définir des chemins.

Comment utiliser

  1. Installer les outils inotify

    Sudo apt-get install intotify-tools

  2. Copiez le script dans un fichier vide, enregistrez-le sous le nom watch_dir.sh

  3. En tête du script, définissez le répertoire à surveiller et à copier les scripts dans
  4. Exécutez-le et il commence à regarder votre répertoire.

2. Utilisation de python

Sans rien installer de plus, nous pouvons cependant faire de même avec un petit script python:

#!/usr/bin/env python3
import subprocess
import os
import time
import shutil

source = "/path/to/sourcedir"
target = "/path/to/targetedir"
files1 = os.listdir(source)

while True:
    time.sleep(2)
    files2 = os.listdir(source)
    # see if there are new files added
    new = [f for f in files2 if all([not f in files1, f.endswith(".sh")])]
    # if so:
    for f in new:
        # combine paths and file
        trg = os.path.join(target, f)
        # copy the file to target
        shutil.move(os.path.join(source, f), trg)
        # and run it
        subprocess.Popen(["/bin/bash", trg])
        print(trg)
    files1 = files2

Comment utiliser

  1. Copiez le script dans un fichier vide, enregistrez-le sous le nom watch_dir.py
  2. Dans l'en-tête du script, configurez le répertoire à surveiller et à copier les scripts dans (source, target)
  3. Exécutez-le et il commence à regarder votre répertoire.

Remarque

Les deux options ci-dessus supposent que les scripts ne nécessitent aucun argument, mais c'est évidemment le cas dans une configuration comme celle-ci.

5
Jacob Vlijm