All of lore.kernel.org
 help / color / mirror / Atom feed
From: Niall Parker <niall@ve7hex.ampr.org>
To: Dave Stubbs <dave.stubbs@utoronto.ca>
Cc: linux-hams@vger.kernel.org
Subject: Re: Soundmodem Logging
Date: Sat, 05 Mar 2005 21:15:34 -0800	[thread overview]
Message-ID: <422A91F6.7010809@ve7hex.ampr.org> (raw)
In-Reply-To: <422A6EFD.3060000@utoronto.ca>

Dave Stubbs wrote:
> Hello all,
> 
> I'm using userspace soundmodem, and it works really great.  However, I 
> have a question about the soundmodem logging setup.
> 
> I have the following in my script that starts up soundmodem:
> 
> soundmodem -sM -v 9
> 
> According to my reading, the -s switch should switch logging to the 
> syslog, and the -v 9 switch should enable massive amounts of logging.
> 
> However, despite this, the syslog only gets one entry showing syslog 
> startup, while the console gets the massive spew of log items.
> 
> Is there any way to redirect all these messages to the syslog instead, 
> where I believe my command line setup told them to go?

Just a guess, but check your syslog.conf file to see what it is doing 
with the messages by facility and loglevel ... it may be receiving them 
OK and then redirecting them to the console.

				... Niall (VE7HEX)

  reply	other threads:[~2005-03-06  5:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-13 18:02 newbie soundmodem question about mic vs line input James Washer
2004-02-13 18:39 ` Jeroen Vreeken
2005-03-06  2:46   ` Soundmodem Logging Dave Stubbs
2005-03-06  5:15     ` Niall Parker [this message]
2005-03-06 12:34       ` Dave Stubbs
2005-03-06 13:12         ` Dave Stubbs
2005-03-06 15:36           ` Tomi Manninen
2005-03-07  4:03             ` Dave Stubbs
2005-03-07  6:24               ` Gérard / F6FGZ
2004-02-13 18:39 ` newbie soundmodem question about mic vs line input Tomi Manninen

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=422A91F6.7010809@ve7hex.ampr.org \
    --to=niall@ve7hex.ampr.org \
    --cc=dave.stubbs@utoronto.ca \
    --cc=linux-hams@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.