public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Xavier Bestel <xavier.bestel@free.fr>
To: Dave Mielke <dave@mielke.cc>
Cc: Whit Blauvelt <whit@transpect.com>,
	Tim Moore <timothymoore@bigfoot.com>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.2.19 Realaudio masq problem
Date: 25 Apr 2001 22:56:11 +0200	[thread overview]
Message-ID: <988232207.32641.4.camel@nomade> (raw)
In-Reply-To: <Pine.LNX.4.30.0104251450550.1012-100000@dave.private.mielke.cc>
In-Reply-To: <Pine.LNX.4.30.0104251450550.1012-100000@dave.private.mielke.cc>

Le 25 Apr 2001 14:52:56 -0400, Dave Mielke a écrit :
> [quoted lines by Whit Blauvelt on April 25, 2001, at 13:38]
> 
> >On Tue, Apr 24, 2001 at 06:01:05PM -0700, Tim Moore wrote:
> >> Try '# strace /usr/bin/X11/realplay On24ram.asp > log' and see where the
> >> connect fails if you aren't getting specific error messages.
> >
> >Unfortunately this spits out a bunch of stuff and then totally freezes up my
> >KDE 2.1.1 desktop.
> 
> strace writes to standard error, not standard output, by default. Better yet,
> though, use the -o option of strace to direct its output to a file, which
> leaves the standard output streams alone for the aplication being traced.

I didn't follow this thread at all (just caught this last mail), but I
use realplayer8 here, and I actually had to *rmmod* the realaudio
masquerading module to make it stream audio from the internet on a
masqueraded machine. The server is a debian with kernel 2.2.19, does
NAT.

Xav


  reply	other threads:[~2001-04-25 21:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-25  1:14 2.2.19 Realaudio masq problem Whit Blauvelt
2001-04-25  1:01 ` Tim Moore
2001-04-25 18:38   ` Whit Blauvelt
2001-04-25 18:52     ` Dave Mielke
2001-04-25 20:56       ` Xavier Bestel [this message]
2001-04-25 23:12         ` Whit Blauvelt
2001-04-26  5:26           ` Xavier Bestel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=988232207.32641.4.camel@nomade \
    --to=xavier.bestel@free.fr \
    --cc=dave@mielke.cc \
    --cc=linux-kernel@vger.kernel.org \
    --cc=timothymoore@bigfoot.com \
    --cc=whit@transpect.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox