Not exactly sure what you are looking to do... you can pipe stderr into
stdout:
command 2>&1 | command-that-receives-both-in-one-stream
or you can dump stdout to a file (or /dev/null) and pipe stderr
command 2>&1 >file | command-gets-stderr
On Tue, Jun 28, 2011 at 4:28 AM, Jesse Molina wrote:
Interesting.
Are there any negative consequences of the workaround?
Also, for fun, anyone got a creative idea how to pipe stderr as an
alternative to redirect? =)
Nicholas Marriott wrote:
> This is a bug in epoll on Linux, you have several choices:
>
> - Build tmux against libevent 2 and s
This is a bug in epoll on Linux, you have several choices:
- Build tmux against libevent 2 and set EVENT_NOEPOLL=1 in the
environment before starting it. (libevent 1.4 has a another bug which
is worse, so only do this if you use libevent 2.)
- Avoid redirecting to /dev/null. IIRC you can work
Sorry. I was working late and was tired. =(
Here's a summary;
Redirecting stdout or stderr from tmux causes indefinite terminal hang.
I had to kill the process from another terminal.
Try this;
tmux info > /dev/null
or maybe
tmux info 1> myfile
Or just try to redirect any output at all
Your message is a bit vague but I guess it is the bug in epoll, use
libevent 2 and run tmux with EVENT_NOEPOLL=1.
On Mon, Jun 27, 2011 at 08:15:38AM -0700, Jesse Molina wrote:
>
> This isn't fun.
>
> tmux has-session -t MYSESSION 2> /dev/null
>
> I need to omit stderr messages and just get th
Looks like bug ID: 3199205
Jesse Molina wrote:
>
> This isn't fun.
>
> tmux has-session -t MYSESSION 2> /dev/null
>
> I need to omit stderr messages and just get the exit status from
> has-session in an if/while statement. Seems like this is totally foobar.
>
>
>
--
# Jesse Molina
# Mail =
