Recherche avancée

Sur d’autres sites (9176)

• MAINTAINERS : Split project server admin list

  6 août 2022, par Michael Niedermayer

  MAINTAINERS : Split project server admin list
  This updates the list closer to reality.
  
  Iam not a professional server admin, iam happy to help maintain the box as i have
  
  done in the past. But iam not qualified nor volunteering to fix sudden problems
  
  nor do i do major upgrades (i lack the experience to recover the box remotely if
  
  something goes wrong) and also iam not maintaining backups ATM (our backup system
  
  had a RAID-5 failure, raz is working on setting a new one up)
  Maybe this should be signaled in a different way than spliting the lines but ATM
  
  people ping me if something is wrong and what i do is mainly mail/ping raz
  
  and try to find another root admin so raz is not the only active & professional
  
  admin on the team. It would be more efficient if people contact raz and others
  
  directly instead of depending on my waking up and forwarding a "ffmpeg.org" is down note
  Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
  

  • [DH] MAINTAINERS

• Documentation #3360 : Mise à jour du profil utilisateur LDAP/SPIP

  18 mai 2016, par svpip -

  b b a écrit :

  Merci pour le retour, la doc me semble claire puisqu’elle ne mentionne pas le champ bio. Aurais-tu une idée de mention à ajouter à l’article pour clarifier la chose ?

  L’utilisateur doit être informé de cette particularité.

  Je propose le texte (à minima dans un premier temps) suivant à intégrer dans http://www.spip.net/fr_article1910.html sous forme de note de bas de page depuis la phrase existante :

  => Les champs remplis sont : nom, login et email qui viennent de LDAP (champs ’cn’, ’uid’ et ’mail’ respectivement) [1]...

  => [1] En complément de ces 3 champs, SPIP propose en option lors de l’installation en mode LDAP, de remplir le champ "bio" pour recevoir les informations issues du champs "description" généralement.
  La valeur récupérée par SPIP depuis le LDAP, lors de la première connexion, ne sera pas mise à jour par la suite.

• do something with script output

  3 novembre 2017, par Opolo Webdesign

  I’m lazy :) so I would like to automate some things on my network. Currently I’m running a script that automatically downloads the series I watch every week. Based on what is downloaded another script searches the web for subtitles. Some downloads however have subtitles with them, so searching for subtitles is not necessary. I would like to check every download for subtitles and get notified (or better move the file) if the file has the correct subtitles.

  I started with the following :

  find /volume2/Downloads/ -type f -mmin -30 | while IFS= read -r file; do
  
      ffmpeg -i "${file}"
  
  done

  This works and shows me the output of the ffmpeg command for each file newer than 30 minutes. I would like to work with the result given by ffmpeg so that when certain characters are present in the output, I’m notified via mail. My Linux scripting skills however stop at the script I got. I’m a web developer so I understand the logic behind a script like this, but not the specific code or commands.

  Characters that I’m looking for :

  • (eng) : Subtitle :
  • (dut) : Subtitle :

  Can this be done ?

  Edit :

  I did some more research and did some changes to my script :

  find /volume2/Downloads/ -type f -mmin -60 | while IFS= read -r file; do
  
      if ffmpeg -i "${file}" | grep -q '(dut): Subtitle:'; then
  
          echo "matched"
  
      fi
  
  done

  Instead of "matched" it shows the ffmpeg output, but it’s probably a step in the right direction ?