[Bug 151440] Re: standard output: Resource temporarily unavailable
And...this problem goes away if I run the same "tail -f" or "read -t 1" loop on a text-only TTY, or under a "screen" session within a terminal emulator. So it's probably a problem with the terminal emulators (MATE terminal and konsole). I'm guessing screen is able to insulate the TTY environment from the GUI emulator enough to sidestep this problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/151440 Title: standard output: Resource temporarily unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/151440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 151440] Re: standard output: Resource temporarily unavailable
Further info: This happens even if I start my "tail -f" process or "read -t 1" loop within a chroot environment running a completely different distro, under an Ubuntu 18.04 terminal. The distro in question (really a custom from- scratch distro) has never had this problem when running as the real root distro. So the root cause of this problem is likely something low-level: either the terminal emulator or the system kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/151440 Title: standard output: Resource temporarily unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/151440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 151440] Re: standard output: Resource temporarily unavailable
Also encountering this issue with "tail -f ", for a log file produced by a script with a LOT of rapid output. Similar issues happen with a simple bash builtin like "read -s -t 1 -N 1 ": it periodically gets in a state where it immediately reports "read: 0: read failed: Resource temporarily unavailable". I initially noticed this with a log watcher script that periodically (every 1s) gathers the tail-end of a log file (same one I'm monitoring with "tail -f" above), then checks for single-character user commands between log polling cycles. I verified that stdin was NOT left in a non-blocking state and managed to reproduce it without even watching the log file or doing anything else (just a tight loop with the above "read" command). This happens a lot more frequently than "tail -f" getting interrupted above, and the event tends to repeat in bursts. This has so far happened under MATE Terminal and konsole, with or without byobu. It does not happen with other distros I've tried. Nothing amiss appears in the system/kernel logs around this time either. Load average on this system commonly reaches 10-16 with almost no swap usage (it's an 8-core+8-thread machine doing various CI builds). I have yet to try it on a text-only TTY, but I suppose I could try that next. System info: Ubuntu 18.04.2 Linux motsognir 4.15.0-45-generic #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/151440 Title: standard output: Resource temporarily unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/151440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
