[Bug 241062] bectl: generated mount should be done in /var/tmp not in /tmp

2020-10-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241062 verma...@interia.pl changed: What|Removed |Added Resolution|--- |Feedback Timeout

[Bug 241062] bectl: generated mount should be done in /var/tmp not in /tmp

2019-10-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241062 --- Comment #3 from Andriy Gapon --- That's strange. I see that the script uses find -x for its job, -x instructs to not traverse mount points... Ah, but then it execs rm -rf -- {} which will happily remove everything under a mountpoint.

[Bug 241062] bectl: generated mount should be done in /var/tmp not in /tmp

2019-10-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241062 --- Comment #2 from verma...@interia.pl --- (In reply to Andriy Gapon from comment #1) The cleartmp script literally wiped one of my mounted BE's. I have backups so it not 'hit' me but that is the point when I got the 'a-ha' moment. --

[Bug 241062] bectl: generated mount should be done in /var/tmp not in /tmp

2019-10-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241062 --- Comment #1 from Andriy Gapon --- Alternative view: whatever cleartmp does it should make sure to not cross mount points. In fact, I believe that cleartmp already obeys that rule. Have you tried to test your scenario (with a throw-away

[Bug 241062] bectl: generated mount should be done in /var/tmp not in /tmp

2019-10-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241062 Bug ID: 241062 Summary: bectl: generated mount should be done in /var/tmp not in /tmp Product: Base System Version: 12.1-RELEASE Hardware: Any OS