It surprises me that nobody has the correct answer to this. Today i faced exactly the same problem and google didn’t help. After 2 hours i found that when placing a file in /etc/cron.d the schedule line has to contain an extra option….. I allways use this for my crontab -e # Minute Hour Day … Read more
Environment Variables If you want to set a number of environment variables into your docker image (to be used within the containers) you can simply use env_file configuration option in your docker-compose.yml file. With that option, all the entries in the .env file will be set as the environment variables in image and hence into … Read more
source your script, don’t execute it like ./foo.sh or sh foo.sh If you execute your script like that, it is running in sub-shell, not your current. source foo.sh would work for you.
‘Hysterical Raisins’, aka Historical Reasons. The explanation from JesperE (or the Bash man page on shell parameter expansion) is accurate for what it does: If $1 exists and is not an empty string, then substitute the quoted list of arguments. Once upon 20 or so years ago, some broken minor variants of the Bourne Shell … Read more
Use utility file, sample usage: $ file /bin/bash /bin/bash: Mach-O universal binary with 2 architectures /bin/bash (for architecture x86_64): Mach-O 64-bit executable x86_64 /bin/bash (for architecture i386): Mach-O executable i386 $ file /etc/passwd /etc/passwd: ASCII English text $ file code.c code.c: ASCII c program text file manual page
You can either write a sed script file and use: sed -f sed.script file1 … Or you can use (multiple) -e ‘command’ options: sed -e ‘/SysAdmin/i\ Linux Scripting’ -e ‘1,$s/A/a/’ file1 … If you want to append something after a line, then: sed -e ‘234a\ Text to insert after line 234’ file1 …
there is a third party tool that can do this. https://github.com/kilobyte/compsize usage: ayush@devbox:/code/compsize$ sudo compsize /opt Processed 54036 files, 42027 regular extents (42028 refs), 27150 inline. Type Perc Disk Usage Uncompressed Referenced Data 82% 5.3G 6.4G 6.4G none 100% 4.3G 4.3G 4.3G zlib 37% 427M 1.1G 1.1G lzo 56% 588M 1.0G 1.0G
I realized my mistake was with iTerm and not with Fish. Press CMD+i with an iTerm window open, then click the Colors tab and set it something nicer. Not sure why this problem didn’t show up before, but it seems like it was triggered by the new Fish installation.
Just like when typing at the shell, you need either a newline or a semicolon before fi: RUN if grep -q “grunt” package.json; then echo succeed; fi add this ^
Use the shell’s appending output redirection (>>) rather than curl’s –output option. curl http://192.99.8.170:8098/stream >> test.pls