Closing this bug with Won't fix as this kernel / release is no longer supported.
Please feel free to open a new bug report if you're still experiencing this on
a newer release (Bionic 18.04.3 / Disco 19.04)
Thanks!
** Changed in: linux (Ubuntu)
Status: Triaged => Won't Fix
** Changed in:
Good to know. If tail works around this by default is there any other
reason to keep the coreutils task open?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/882147
Title:
tail -f works because it checks the file every sleep-interval seconds (defaults
to 1 second).
tail -f -s 10 /var/log/syslog gives a burst of new lines every 10 seconds.
With this test I see 10-seconds bursts with linux 4.10.0 and 4.13.0
indicating this bug isn't fixed.
--
You received this bug
tail -f /var/log/syslog worked for me with 17.10 dev | kernel 4.12.
(Tested by turning network on and off).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/882147
Title:
Nope, tail -f is still broken at least in 4.12.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/882147
Title:
overlayfs does not implement inotify interfaces correctly
I've seen reports that this is fixed in 4.10?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/882147
Title:
overlayfs does not implement inotify interfaces correctly
According to some here: https://github.com/phusion/baseimage-
docker/issues/198 this issue with overlayfs is not allowing CROND to run
in a docker container. I would really appreciate some eyes on this
issue if that is the case.
--
You received this bug notification because you are a member of
@Alf Gaida Most ppl can't read, it's unfortunate. To communicate with
ppl one must repeat themselves like an advertiser a 100 times, no a 1000
times is not even enough. Computers read vary well and what's more is
if you adjust your phrasing slightly enough times eventually you'll get
total
@Mike Mestnik: you can repeat yourself as often as you want to - this is
a bug and should be addressed soon. There is absolutely no need to argue
- there is a need for fixing faulty behaviour. Ok. might not be your
thing, because may be complicated. Writing nonsense is not, therefore
you prefer
@Mike Mestnik: To be true, i have a record that shows that i'm not the
nicest and most patient living person in the world - but you should look
at the bigger picture. I've used aufs for ISOs long term - with the
latest development in debian aufs does more harm than good - so the
logical switch is
This is currently causing some problems for me -- I'm using grub2 to
boot a LiveISO with TORAM=Yes from a DiskOnModule to implement a
hardware appliance.
It's *REALLY* aggravating that tail -f /var/log/filename does not work
as expected.
Could someone bring that overlayfs inotify kernel patch up
Notice the comment #30 above:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/882147/comments/30
Also note that there is some confusion about known behavior of released
kernels. I suggest that if a kernel is released and it's select() call
does not behave appropriately that every
12 matches
Mail list logo
