4 ms·
Reminds me of a time a coworker at a previous job almost brought down a production server by opening a file in vi. That file was a customer log that had grown
by lobotryas 13y ago
Reminds me of a time a coworker at a previous job almost brought down a production server by opening a file in vi.
That file was a customer log that had grown to 100+gb in size due to an error that she was debugging. She failed to check the log size, instead assuming that it was a small file left over after that night's log rotation. When vi tried to load the file to memory, it almost crashed the box before we could kill it (we still got calls about degraded performance though).
- FuzzyDunlop 13y agoI've made this mistake, only I was too naïve at the time to realise my mistake, thinking that vim, because of its reputation, could surely handle it. A server reboot later and I was enlightened.