Scary. Even more scary is the fact that the bug has been open for a week, one person has confirmed 100% reproducibility, and no one seems to care at Red Hat. Isn't deleting peoples hard drives a big no no ?
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.
Bug 1202858 – Restarting squid results in deleting all files in hard-drive
61–70 of 179 posts
Re: Bug 1202858 – Restarting squid results in deleting all files in hard-drive
#62Earlier quoted context omitted.
As someone who uses the commandline a lot but isn't exactly a wizard, why does this work?
The * is expanded by the shell to a space-delimited list of filenames, but the shell does not adequately escape filenames that can be misinterpreted as arguments to 'rm'.
Re: Bug 1202858 – Restarting squid results in deleting all files in hard-drive
#63We had one of these kinda bugs. If you uninstalled our software it deleted a major chunk of your Windows registry, crippling your computer. It was a one character error in our script. The first ticket read "Uninstalling [Product] destroys your computer". I was responsible for customer support. Good times! Was a rough week. We managed to not get sued.
Pretty terrible that such a thing is even allowed by Windows. This is why as a user I like Apple's OS X sandbox.
Re: Bug 1202858 – Restarting squid results in deleting all files in hard-drive
#64Earlier 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.
Is there an aricle with specifics on this and why it was done?
Re: Bug 1202858 – Restarting squid results in deleting all files in hard-drive
#65Earlier quoted context omitted.
Is there an aricle with specifics on this and why it was done?
I have no direct information about this specific case, but in ye olden Unix™ days, there was no /sbin, so all those binaries instead lived in /etc. The Red Hat symlinks could be a backwards-compatibility thing.
Re: Bug 1202858 – Restarting squid results in deleting all files in hard-drive
#66Re: Bug 1202858 – Restarting squid results in deleting all files in hard-drive
#67Re: Bug 1202858 – Restarting squid results in deleting all files in hard-drive
#68I love how deadpan the bug report is: Actual results: All files are deleted on the machine. Expected results: Squid is restarted. Not many details yet but it sounds similar to the Steam bug [0] from last year. [0] https://github.com/valvesoftware/steam-for-linux/issues/3671
Stopping squid: ................[ OK ]
rm: cannot remove `/boot': Device or resource busyRe: Bug 1202858 – Restarting squid results in deleting all files in hard-drive
#69Scary. Even more scary is the fact that the bug has been open for a week, one person has confirmed 100% reproducibility, and no one seems to care at Red Hat. Isn't deleting peoples hard drives a big no no ?
Well, the bug was reported against RHEL 6.7 which has not been released yet.
Re: Bug 1202858 – Restarting squid results in deleting all files in hard-drive
#70Earlier quoted context omitted.
The * is expanded by the shell to a space-delimited list of filenames, but the shell does not adequately escape filenames that can be misinterpreted as arguments to 'rm'.
That's kind of scary — in that case I guess I should avoid creating a file named -rf.
Can someone knowledgeable about the shell expand on this? I don't dare test it on my machine.