Check These Out
I wasted two hours reading the sox documentation and searching on the web for the format of some obscure fscking sound sample, and then finally came up with this. This plays only the first three seconds of your unknown formatted sound file using every one of sox's built-in filetypes. If you don't get an exact match, you may get close.
.
I could not fit every single type in and keep it under 127 characters, so you will have to replace "..." with the full list obtainable by `$ sox --help` (or try `Show sample output`)
.
note: /usr/bin/play should be linked to sox on most systems.
XX is your device partition number like /dev/sdc1 .
to see how many inodes your partition have type:
$ df --inodes (or df -i)
Default formatting with ext4 would create small inode count for the new partition
if you need big count of inodes is the fstype news the correct one.
in debian you can see which fstype exists as template in:
$ vim /etc/mke2fs.conf
if you format default ext for a partition size with 1TB you would get 1 Million inodes (not enough for backupStorages)
but if you format with fstype news you would get hunderd of millions of inodes for the partition.
you have tune
$/etc/sysctl.conf
also with following sysconfig parameters
$ fs.file-max = XXX
$ fs.nr_open = XXX
where XXX is the count of max inodes for whole system
Works for most distributions, tested on Ubuntu, Fedora, CentOS, Gentoo, SUSE, RedHat.
Debian and Slackware:
$cat /etc/*version
Generates the list of clients (IPs addresses) that have used the Squid webproxy according to the most recent log. Every IP appears only once in the list.
swap out "80" for your port of interest. Can use port number or named ports e.g. "http"
Lots of fun to run on nfs clients when the server or network connection is having issues
Create transparent image to use as icon, watermark for other images, etc.
Randomly decide whether to run a command, or fail.
It's useful for testing purposes.
.
Usage: ran PERCENTAGE COMMAND [ARGS]
Note: In this version the percentage is required.
.
This is like @sesom42 and @snipertyler's commands but in a USABLE form.
.
e.g. In your complicated shell script, put "ran 99" before a crucial component.
Now, it will fail 1% of the time allowing you to test the failure code-path.
$ ran 99 my_complex_program arg1 arg2