[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/151440
Ti
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
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
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 unavail
Hi,
I met this issue today, and my machine info is
Linux yonglong 4.4.0-142-generic #168~14.04.1-Ubuntu SMP Sat Jan 19
11:26:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Every time the log is "tee: 'standard output': Resource temporarily
unavailable".
tee (GNU coreutils) 8.21
Hi,
I met this issue today.
Linux yonglong 4.4.0-142-generic #168~14.04.1-Ubuntu SMP Sat Jan 19 11:26:28
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/
Hi,
I met this issue today, and my machine info is
Linux yonglong 4.4.0-142-generic #168~14.04.1-Ubuntu SMP Sat Jan 19
11:26:28 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://
Hi,
I met this issue today, and my machine info is
Linux yonglong 4.4.0-142-generic #168~14.04.1-Ubuntu SMP Sat Jan 19
11:26:28 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:/
Hi,
I am also experiencing this issues recently in my machine 4.15.0-45-generic
#48~16.04.1-Ubuntu
which doesn't yield any log rather than
"tee: 'standard output': Resource temporarily unavailable"
Moreover, I haven't seen this before, I used to get my work logs
previously too. but this is str
** Changed in: linux (Ubuntu)
Status: Invalid => New
--
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 abo
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would
appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.
There are one of two ways you should be able to test:
1) If you are comfortable
Hi Daniel,
If an when you are able to test Hardy, please let us know your results.
Thanks.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
standard output: Resource temporarily unavailable
https://bugs.launchpad.net/bugs/151440
You received this bug notification because you ar
Hi Michael,
Unfortunately I am not able to reproduce the situation, since I am not
yet running Hardy.
BR,
Daniel
On Mon, Aug 4, 2008 at 11:06 PM, Michael Nagel <[EMAIL PROTECTED]> wrote:
> copied text from mentioned blog:
>
> July 3, 2008
>
> And now I'm remembering why replacing the command lin
copied text from mentioned blog:
July 3, 2008
And now I'm remembering why replacing the command line utilities out of
Ubuntu is so vital to getting a reliable build:
tee: standard output: Resource temporarily unavailable
tee: write error
The forkbomb script pipes the output of the build
is this still broken with hardy?
--
standard output: Resource temporarily unavailable
https://bugs.launchpad.net/bugs/151440
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:
Here's another report of this bug (from a blog-type post):
http://landley.net/notes.html#03-07-2008
--
standard output: Resource temporarily unavailable
https://bugs.launchpad.net/bugs/151440
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
17 matches
Mail list logo
