Bug 1202858 – Restarting squid results in deleting all files in hard-drive

Post by woah » Tue, Mar 24, 2015, 8:52 AM UTC

jiffytick wrote: post #35

lpsz wrote: post #32

Earlier quoted context omitted.

And this is why it is important to write something like set -eu on top of your bash scripts -- execution will stop on errors (non-zero retvals) and on undefined variables.

or check the variable before using it, like any other programming language: [[ "$VAR" ]] && rm -rf "$VAR/*" I think most of these issues stem from the fact that most developers that write shell scripts don't actually understand what they're doing, treating the script as a necessary annoyance rather than a component of the software.

Post by michaelx386 » Tue, Mar 24, 2015, 8:56 AM UTC

ioquatix wrote: post #56

jedisct1 wrote: post #47

My good old trick to mitigate that is: touch /-@ I also always do it in my home directory: touch ~/-@ That's the first thing I do on a new host. When accidentally running rm -f *, the command expands to -@ first, which is not a valid option and makes the command fail before doing any harm rm: illegal option -- @ usage: rm [-f | -i] [-dPRrvW] file ...

Or just use zsh.

Post by rwmj » Tue, Mar 24, 2015, 8:58 AM UTC

cssmoo wrote: post #69

oogway wrote: post #14

Earlier quoted context omitted.

Well, the bug was reported against RHEL 6.7 which has not been released yet.

RH don't have a great reputation here. Unlike Debian which does proper triage and practices "zero release-critical bugs", RH threw out RHEL7 with loads of critical issues still open.

Post by Tiksi » Tue, Mar 24, 2015, 9:25 AM UTC

Erwin wrote: post #72

cellularmitosis wrote: post #40

Earlier quoted context omitted.

Ahh Redhat, the distro which chose to symlink a bunch of binary lib files from Apache into the etc directory. "Why is grepping /etc taking so long? Binary files in /etc?!? WTF?!?" Coming from Debian, Redhat seems to make a lot of irk-worthy choices.

I find the /etc/httpd/logs symlink more annoying. If you want to grep through your Apache configuration you have to explicitly grep through conf and conf.d otherwise just going to /etc/httpd and doing a grep -r you're searching through gigs of Apache logs.

      -d, --directories=ACTION  how to handle directories;
                            ACTION is 'read', 'recurse', or 'skip'
      -D, --devices=ACTION      how to handle devices, FIFOs and sockets;
                            ACTION is 'read' or 'skip'
      -r, --recursive           like --directories=recurse
      -R, --dereference-recursive  likewise, but follow all symlinks

Post by phireal » Tue, Mar 24, 2015, 9:43 AM UTC

michaelx386 wrote: post #83

ioquatix wrote: post #56

Earlier quoted context omitted.

Or just use zsh.

Would zsh still protect me if the script explicitly uses Bash (i.e. #!/bin/bash)? Sorry if this is a dumb question, I'm unsure how shells work when calling other kinds of shell scripts.