Recherche avancée

Sur d’autres sites (3213)

• How can I delete all folders of a specific name without deleting Contents in it [on hold]

  17 janvier 2015, par Chatcafe

  How do I delete all Folders with a specific name (e.g. 128Kbps_Songs) without deleting its files

  For example if I have directory "MP3_SONGS" with subdirectories "A", "B", "C" and each subdirectory has MANY directory Contains Film Name "FILM_NAME1", "FILM_NAME2", "FILM_NAME3" in it, In That Each Film NAme I have specific Folder NAme (128Kbps_Songs) in this "128Kbps_Songs" Folder I have That Film mp3 Songs Files
  
  
  
  how can I remove the Folder "128Kbps_Songs", in Each Film_Name directory and Have to get these mp3 songs in that FILM_NAME.. ( Have to Delete 128Kbps_Songs Folder in all FILM_NAME without deleting the mp3 Songs in it, have to get the mp3 in FILM_NAME Directory..
  
  
  
  
  
  MP3_SONGS (Parent Directory) ------ A , B, C
  
  
  
  A (Sub Directory1) ------ FILM_NAME1 , FILM_NAME2
  
  B (Sub Directory2) ------ FILM_NAME3 , FILM_NAME4
  
  c (Sub Directory3) ------ FILM_NAME5 , FILM_NAME6
  
  
  
  FILM_NAME1 (Directory) ---- 128Kbps_Songs (Directory) ------ FILM_NAME1(MP3 Files)
  
  FILM_NAME2 (Directory) ---- 128Kbps_Songs (Directory) ------ FILM_NAME2(MP3 Files)
  
  
  
  FILM_NAME3 (Directory) ---- 128Kbps_Songs (Directory) ------ FILM_NAME3 MP3 Files
  
  FILM_NAME4 (Directory) ---- 128Kbps_Songs (Directory) ------ FILM_NAME4 MP3 Files
  
  
  
  FILM_NAME5 (Directory) ---- 128Kbps_Songs (Directory) ------ FILM_NAME5 MP3 Files
  
  FILM_NAME6 (Directory) ---- 128Kbps_Songs (Directory) ------ FILM_NAME6 MP3 Files
  
  
  
  Need Files in:
  
  FILM_NAME1 (Directory)  ------ FILM_NAME1 MP3 Files
  
  
  
  FILM_NAME2 (Directory)  ------ FILM_NAME2 MP3 Files
  
  
  
  FILM_NAME3 (Directory)  ------ FILM_NAME3 MP3 Files
  
  
  
  FILM_NAME4 (Directory)  ------ FILM_NAME4 MP3 Files
  
  
  
  FILM_NAME5 (Directory)  ------ FILM_NAME5 MP3 Files
  
  
  
  FILM_NAME6 (Directory)  ------ FILM_NAME6 MP3 Files
  
  
  
  > if 128Kbps_Songs directory exits there only want this changes

• What is data anonymization in web analytics ?

  11 février 2020, par Joselyn Khor — Analytics Tips, Privacy
  Collecting information via web analytics platforms is needed to help a website grow and improve. When doing so, it’s best to strike a balance between getting valuable insights, and keeping the trust of your users by protecting their privacy.

  This means not collecting or processing any personally identifiable information (PII). But what if your organisation requires you to collect PII ?

  That’s where data anonymization comes in.

  

  What is data anonymization ?

  Data anonymization makes identifiable information unidentifiable. This is done through data processing techniques which remove or modify PII data. So data becomes anonymous and can’t be linked to any individual.

  In the context of web analytics, data anonymization is handy because you can collect useful data while protecting the privacy of website visitors.

  Why is data anonymization important ?

  Through modern threats of identity theft, credit card fraud and the like, data anonymization is a way to protect the identity and privacy of individuals. As well as protect private and sensitive information of organisations. 

  Data anonymization lets you follow the many laws around the world which protect user privacy. These laws provide safeguards around collecting personal data or personally identifiable information (PII), so data anonymization is a good solution to ensure you’re not processing such sensitive information.

  In some cases, implementing data anonymization techniques means you can avoid having to show your users a consent screen. Which means you may not need to ask for consent in order to track data. This is a bonus as consent screens can annoy and stop people from engaging with your site.

  GDPR and data anonymization

  

  The GDPR is a law in the EU that limits the collection and processing of personal data. The aim is to give people more control over their online personal information. Which is why website owners need to follow certain rules to become GDPR compliant and protect user privacy. According to the GDPR, you can be fined up to 4% of your yearly revenue for data breaches or non-compliance. 

  In the case of web analytics, tools can be easily made compliant by following a number of steps. 

  This is why anonymizing data is a big deal.

  Anonymized data isn’t personal data according to the GDPR : 

  “The principles of data protection should therefore not apply to anonymous information, namely information which does not relate to an identified or identifiable natural person or to personal data rendered anonymous in such a manner that the data subject is not or no longer identifiable.”

  This means, you still get the best of both worlds. By anonymizing data, you’re still able to collect useful information like visitor behavioural data.

  US privacy laws and data anonymization

  In the US, there isn’t one single law that governs the protection of personal data, called personally identifiable information (PII). There are hundreds of federal and state laws that protect the personal data of US residents. As well as, industry-specific statutes related to data privacy, like the California Consumer Privacy Act (CCPA) and the Health Insurance Portability and Accountability Act (HIPAA).

  Website owners in the US need to know exactly what laws govern their area of business in order to follow them.

  A general guideline is to protect user privacy regardless of whether you are or aren’t allowed to collect PII. This means anonymizing identifiable information so your website users aren’t put at risk.

  Data anonymization techniques in Matomo Analytics

  If you carry these out, you won’t need to ask your website visitors for tracking consent since anonymized data is no longer considered personal data under the GDPR.

  • Anonymize previously tracked raw data – like visitors/visits
  • Anonymize Visitor IP addresses
  • Anonymize geo-location information (country, region, city)
  • Pseudonymize User ID ( if you don’t want this data to land on your Matomo server, the solution is simply to not set the User ID. Then Matomo will use the normal anonymized IDs)
  • Data can also be anonymized before it’s even sent to Matomo
  • Learn how to further configure privacy settings in a web analytics tool like Matomo
  • 11 ways Matomo Analytics helps you to protect your visitors privacy

  The techniques listed above make it easy for you when using a tool like Matomo, as they are automatically anonymized.

  Tools like Google Analytics on the other hand don’t provide some of the privacy options and leave it up to you to take on the burden of implementation without providing steps.

  Data anonymization tools

  If you’re a website owner who wants to grow your business or learn more about your website visitors, privacy-friendly tools like Matomo Analytics are a great option. By following the easy steps to be GDPR compliant, you can anonymize all data that could put your visitors at risk.

• Statically built FFMPEG binary segmentation fault

  12 février 2020, par stevendesu

  I want to create a custom build of FFMPEG which rips out everything except for the ability to transmux HLS videos to MP4, and I need this build to be 100% static with no external dependencies

  I tried using the following configuration :

  ./configure \
  
      --extra-cflags='-static -static-libstdc++ -static-libgcc' \
  
      --extra-cxxflags='-static -static-libstdc++ -static-libgcc' \
  
      --extra-ldflags='-static -static-libstdc++ -static-libgcc' \
  
      --pkg-config-flags='--static' \
  
      --enable-static \
  
      --disable-shared \
  
      --disable-runtime-cpudetect \
  
      --disable-autodetect \
  
      --disable-ffplay \
  
      --disable-ffprobe \
  
      --disable-doc \
  
      --disable-avdevice \
  
      --disable-swresample \
  
      --disable-swscale \
  
      --disable-postproc \
  
      --disable-pthreads \
  
      --disable-w32threads \
  
      --disable-os2threads \
  
      --enable-network \
  
      --disable-dct \
  
      --disable-dwt \
  
      --disable-error-resilience \
  
      --disable-lsp \
  
      --disable-lzo \
  
      --disable-mdct \
  
      --disable-rdft \
  
      --disable-fft \
  
      --disable-faan \
  
      --disable-pixelutils \
  
      --disable-encoders \
  
      --disable-decoders \
  
      --disable-hwaccels \
  
      --disable-muxers \
  
      --enable-muxer=mov \
  
      --enable-muxer=mp4 \
  
      --disable-demuxers \
  
      --enable-demuxer=hls \
  
      --enable-demuxer=mpegts \
  
      --enable-demuxer=h264 \
  
      --enable-demuxer=aac \
  
      --disable-parsers \
  
      --enable-parser=h264 \
  
      --enable-parser=aac \
  
      --disable-bsfs \
  
      --disable-protocols \
  
      --enable-protocol=tcp \
  
      --enable-protocol=tls \
  
      --enable-protocol=http \
  
      --enable-protocol=https \
  
      --enable-protocol=hls \
  
      --disable-indevs \
  
      --disable-outdevs \
  
      --disable-devices \
  
      --disable-filters \
  
      --disable-alsa \
  
      --disable-appkit \
  
      --disable-avfoundation \
  
      --disable-bzlib \
  
      --disable-coreimage \
  
      --disable-iconv \
  
      --disable-lzma \
  
      --enable-openssl \
  
      --disable-sndio \
  
      --disable-sdl2 \
  
      --disable-securetransport \
  
      --disable-xlib \
  
      --disable-zlib \
  
      --disable-amf \
  
      --disable-audiotoolbox \
  
      --disable-cuda-llvm \
  
      --disable-cuvid \
  
      --disable-d3d11va \
  
      --disable-dxva2 \
  
      --disable-ffnvcodec \
  
      --disable-nvdec \
  
      --disable-nvenc \
  
      --disable-v4l2-m2m \
  
      --disable-vaapi \
  
      --disable-vdpau \
  
      --disable-videotoolbox \
  
      --disable-debug

  This looked about like what I wanted :

  install prefix            /usr/local
  
  source path               .
  
  C compiler                gcc
  
  C library                 glibc
  
  ARCH                      x86 (generic)
  
  big-endian                no
  
  runtime cpu detection     no
  
  standalone assembly       yes
  
  x86 assembler             nasm
  
  MMX enabled               yes
  
  MMXEXT enabled            yes
  
  3DNow! enabled            yes
  
  3DNow! extended enabled   yes
  
  SSE enabled               yes
  
  SSSE3 enabled             yes
  
  AESNI enabled             yes
  
  AVX enabled               yes
  
  AVX2 enabled              yes
  
  AVX-512 enabled           yes
  
  XOP enabled               yes
  
  FMA3 enabled              yes
  
  FMA4 enabled              yes
  
  i686 features enabled     yes
  
  CMOV is fast              yes
  
  EBX available             yes
  
  EBP available             yes
  
  debug symbols             no
  
  strip symbols             yes
  
  optimize for size         no
  
  optimizations             yes
  
  static                    yes
  
  shared                    no
  
  postprocessing support    no
  
  network support           yes
  
  threading support         no
  
  safe bitstream reader     yes
  
  texi2html enabled         no
  
  perl enabled              yes
  
  pod2man enabled           yes
  
  makeinfo enabled          no
  
  makeinfo supports HTML    no
  
  
  
  External libraries:
  
  openssl
  
  
  
  External libraries providing hardware acceleration:
  
  
  
  Libraries:
  
  avcodec                 avfilter                avformat                avutil
  
  
  
  Programs:
  
  ffmpeg
  
  
  
  Enabled decoders:
  
  
  
  Enabled encoders:
  
  
  
  Enabled hwaccels:
  
  
  
  Enabled parsers:
  
  aac                     h264
  
  
  
  Enabled demuxers:
  
  aac                     h264                    hls                     mpegts
  
  
  
  Enabled muxers:
  
  mov                     mp4
  
  
  
  Enabled protocols:
  
  hls                     http                    https                   tcp                     tls
  
  
  
  Enabled filters:
  
  aformat                 anull                   atrim                   format                  hflip                   null                    transpose               trim                    vflip
  
  
  
  Enabled bsfs:
  
  null
  
  
  
  Enabled indevs:
  
  
  
  Enabled outdevs:
  
  
  
  License: LGPL version 2.1 or later

  It included several filters which I won’t ever need or use, but these filters are pulled in automatically if you don’t specify --disable-avfilter, and specifying --disable-avfilter prevents the ffmpeg binary from being produced. So I’m stuck with those.

  Using these parameters and then running make, I received a binary that was about 5.9 MB in size and looked right :

  $> ldd ffmpeg
  
          not a dynamic executable

  But when I try to run it :

  $> ./ffmpeg -version
  
  Segmentation fault

  Using valgrind to try and inspect the cause of the segmentation fault :

  $> valgrind ./ffmpeg -version
  
  .... lots of stuff ...
  
  ==61362== Jump to the invalid address stated on the next line
  
  ==61362==    at 0x0: ???
  
  ==61362==    by 0x70BB1B: ??? (in /src/FFmpeg/ffmpeg)
  
  ==61362==    by 0x70B2E6: ??? (in /src/FFmpeg/ffmpeg)
  
  ==61362==    by 0x4033F9: ??? (in /src/FFmpeg/ffmpeg)
  
  ==61362==    by 0x1FFF000677: ???
  
  ==61362==  Address 0x0 is not stack'd, malloc'd or (recently) free'd
  
  ==61362==
  
  ==61362==
  
  ==61362== Process terminating with default action of signal 11 (SIGSEGV)
  
  ==61362==  Bad permissions for mapped region at address 0x0
  
  ==61362==    at 0x0: ???
  
  ==61362==    by 0x70BB1B: ??? (in /src/FFmpeg/ffmpeg)
  
  ==61362==    by 0x70B2E6: ??? (in /src/FFmpeg/ffmpeg)
  
  ==61362==    by 0x4033F9: ??? (in /src/FFmpeg/ffmpeg)
  
  ==61362==    by 0x1FFF000677: ???
  
  ==61362==
  
  ==61362== HEAP SUMMARY:
  
  ==61362==     in use at exit: 0 bytes in 0 blocks
  
  ==61362==   total heap usage: 0 allocs, 0 frees, 0 bytes allocated
  
  ==61362==
  
  ==61362== All heap blocks were freed -- no leaks are possible
  
  ==61362==
  
  ==61362== For counts of detected and suppressed errors, rerun with: -v
  
  ==61362== Use --track-origins=yes to see where uninitialised values come from
  
  ==61362== ERROR SUMMARY: 93 errors from 90 contexts (suppressed: 0 from 0)
  
  Segmentation fault

  Attempting to access memory at location 0x0 sounds like trying to follow a null pointer. But I’m not sure how to fix this.

  gdb backtrace

  When I first ran gdb ./ffmpeg gdb immediately gave me a segmentation fault and I wasn’t kicked into the gdb REPL, so I couldn’t investigate

  After rebuilding ffmpeg I was able to get in this time :

  $> gdb ./ffmpeg
  
  
  
  GNU gdb (Ubuntu 8.1-0ubuntu3.2) 8.1.0.20180409-git
  
  Copyright (C) 2018 Free Software Foundation, Inc.
  
  License GPLv3+: GNU GPL version 3 or later /gnu.org/licenses/gpl.html>
  
  This is free software: you are free to change and redistribute it.
  
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  
  and "show warranty" for details.
  
  This GDB was configured as "x86_64-linux-gnu".
  
  Type "show configuration" for configuration details.
  
  For bug reporting instructions, please see:
  
  /www.gnu.org/software/gdb/bugs/>.
  
  Find the GDB manual and other documentation resources online at:
  
  /www.gnu.org/software/gdb/documentation/>.
  
  For help, type "help".
  
  Type "apropos word" to search for commands related to "word"...
  
  Reading symbols from ffmpeg...done.
  
  (gdb) r
  
  Starting program: /src/FFmpeg/ffmpeg
  
  warning: Error disabling address space randomization: Operation not permitted
  
  
  
  Program received signal SIGSEGV, Segmentation fault.
  
  0x0000000000000000 in ?? ()
  
  (gdb) bt
  
  #0  0x0000000000000000 in ?? ()
  
  #1  0x0000000000f9a8d5 in __register_frame_info_bases.part.6 ()
  
  #2  0x00000000004445fd in frame_dummy ()
  
  #3  0x0000000000000001 in ?? ()
  
  #4  0x0000000000ebd20c in __libc_csu_init ()
  
  #5  0x0000000000ebc9d7 in __libc_start_main ()
  
  #6  0x000000000044451a in _start ()
  
  (gdb)

  I tried grep’ing the code base for __register_frame_info_bases and found nothing. So I’m not really sure where to go from here

  A fix, but not an explanation

  By randomly removing configuration parameters and rebuilding I discovered that --disable-pthreads was causing the segmentation fault. When I remove this, ffmpeg runs just fine

  I don’t know why this is the case, though. Why would they make it possible to remove something that you need to run ?