4 ms·
I dunno how I missed this until now, but the lightning talk on tail -f is great https://www.youtube.com/watch?v=vm1GJMp0QN4#t=41m18s https://www.youtube.com/wa
by justinsaccount 9y ago
I dunno how I missed this until now, but the lightning talk on tail -f is great
https://www.youtube.com/watch?v=vm1GJMp0QN4#t=41m18s https://www.youtube.com/watch?v=vm1GJMp0QN4#t=41m18s
When you realize halfway through that the implementations of tail -f you've written are probably broken too :(
- lamby 9y agoJust watched this. It's really fun, thanks :)
- dozzie 9y agoWell, my `tail' (GNU coreutils) watches the file for being truncated. So does a log file follower that I wrote. Is it really that difficult to imagine the log can shrink, especially if one spent plenty of time in logrotate's configuration? There are many daemons that can't reopen their log file.
- raattgift 9y agocan't? good grief. Can you trick them into logging into a FIFO, at least? Then put something sensible on the other end draining into regualr files that typical followers/processors can deal with at their pleasure?
- ketralnis 9y agoDepends on the daemon. The most common version of this would be a daemon that starts as root, opens its log file, and then drops privs. In that simple case, yeah going to a named pipe would work fine. But if you stop reading from the pipe, it will presumably block when writing.