Recherche avancée

Médias (0)

Mot : - Tags -/latitude

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (111)

  • Script d’installation automatique de MediaSPIP

    25 avril 2011, par

    Afin de palier aux difficultés d’installation dues principalement aux dépendances logicielles coté serveur, un script d’installation "tout en un" en bash a été créé afin de faciliter cette étape sur un serveur doté d’une distribution Linux compatible.
    Vous devez bénéficier d’un accès SSH à votre serveur et d’un compte "root" afin de l’utiliser, ce qui permettra d’installer les dépendances. Contactez votre hébergeur si vous ne disposez pas de cela.
    La documentation de l’utilisation du script d’installation (...)

  • Automated installation script of MediaSPIP

    25 avril 2011, par

    To overcome the difficulties mainly due to the installation of server side software dependencies, an "all-in-one" installation script written in bash was created to facilitate this step on a server with a compatible Linux distribution.
    You must have access to your server via SSH and a root account to use it, which will install the dependencies. Contact your provider if you do not have that.
    The documentation of the use of this installation script is available here.
    The code of this (...)

  • Que fait exactement ce script ?

    18 janvier 2011, par

    Ce script est écrit en bash. Il est donc facilement utilisable sur n’importe quel serveur.
    Il n’est compatible qu’avec une liste de distributions précises (voir Liste des distributions compatibles).
    Installation de dépendances de MediaSPIP
    Son rôle principal est d’installer l’ensemble des dépendances logicielles nécessaires coté serveur à savoir :
    Les outils de base pour pouvoir installer le reste des dépendances Les outils de développements : build-essential (via APT depuis les dépôts officiels) ; (...)

Sur d’autres sites (10089)

  • Still getting FFMPEG "Segmentation fault" with network stream source with the AmazonLinux 2023 distro [closed]

    28 décembre 2023, par Matthew Drooker

    After referencing https://docs.yucca.app/en/troubleshooting/Segmentation_fault_core_dumped

    


    And using

    


    FFMPEG "Segmentation fault" with network stream source

    


    I thought I had this solved.
But still having the same issue as documented as fixed.

    


    Im using AmazonLinux 2023 distro in a Lambda custom image.

    


    Im trying to use baseImage from FROM --platform=linux/amd64 public.ecr.aws/lambda/nodejs:20

    


    Then doing- RUN dnf install nscd  -y in my Dockerfile allowing the nscd service to be installed per the answer.

    


    But, Im still getting the ffprobe was killed with signal SIGSEGV error with the new AmazonLinux Distro.

    


    Has anyone else faced this with the 2023 Distro ? Or have an answer to this question ?

    


  • ffmpeg not working with filenames that have whitespace

    18 mai 2021, par cmw

    I'm using FFMPEG to measure the duration of videos stored in an Amazon S3 Bucket.

    


    I've read the FFMPEG docs, and they explicitly state that all whitespace and special characters need to be escaped, in order for FFMPEG to handle them properly :

    


    See docs 2.1 and 2.1.1 : https://ffmpeg.org/ffmpeg-utils.html

    


    However, when dealing with files whose filenames contain whitespace, ffmpeg fails to render a result.

    


    I've tried the following, with no success

    


    ffmpeg -i "http://s3.mybucketname.com/videos/my\ video\ file.mov" 2>&1 | grep Duration | awk '{print $2}' | tr -d
ffmpeg -i "http://s3.mybucketname.com/videos/my video file.mov" 2>&1 | grep Duration | awk '{print $2}' | tr -d
ffmpeg -i "http://s3.mybucketname.com/videos/my'\' video'\' file.mov" 2>&1 | grep Duration | awk '{print $2}' | tr -d
ffmpeg -i "http://s3.mybucketname.com/videos/my\ video\ file.mov" 2>&1 | grep Duration | awk '{print $2}' | tr -d


    


    However, if I strip out the whitespace in the filename – all is well, and the duration of the video is returned.

    


  • ffmpeg not working with filenames that have whitespace

    1er avril 2017, par cmw

    I’m using FFMPEG to measure the duration of videos stored in an Amazon S3 Bucket.

    I’ve read the FFMPEG docs, and they explicitly state that all whitespace and special characters need to be escaped, in order for FFMPEG to handle them properly :

    See docs 2.1 and 2.1.1 : https://ffmpeg.org/ffmpeg-utils.html

    However, when dealing with files whose filenames contain whitespace, ffmpeg fails to render a result.

    I’ve tried the following, with no success

    ffmpeg -i "http://s3.mybucketname.com/videos/my\ video\ file.mov" 2>&1 | grep Duration | awk '{print $2}' | tr -d
    
ffmpeg -i "http://s3.mybucketname.com/videos/my video file.mov" 2>&1 | grep Duration | awk '{print $2}' | tr -d
    
ffmpeg -i "http://s3.mybucketname.com/videos/my'\' video'\' file.mov" 2>&1 | grep Duration | awk '{print $2}' | tr -d
    
ffmpeg -i "http://s3.mybucketname.com/videos/my\ video\ file.mov" 2>&1 | grep Duration | awk '{print $2}' | tr -d

    However, if I strip out the whitespace in the filename – all is well, and the duration of the video is returned.

    Any help is appreciated !

Navigation