Borden Rhodes <j...@bordenrhodes.com> writes:
> Since there's almost no documentation as to what can be safely rm'd in
> /var without breaking your system, I decide the least risky choice is
> to sudo rm -rf the offending 3-gig syslog file from single-user mode
> and the systemd debug shell. But *THIS* command failed because there
> was 'no space left on the device'. Is this right? Does rm need space
> on a drive to free other space?
Yes, this is right. The problem is not 'rm', the problem is that you use
sudo without understanding why it is set up like that: sudo logs the
command it executes to /var/log/auth.log
--
"We will need a longer wall when the revolution comes."
--- AJS, quoting an uncertain source.
