linux-hams.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Stubbs <dave.stubbs@utoronto.ca>
To: linux-hams@vger.kernel.org
Subject: Re: Soundmodem Logging
Date: Sun, 06 Mar 2005 08:12:29 -0500	[thread overview]
Message-ID: <422B01BD.8030509@utoronto.ca> (raw)
In-Reply-To: <422AF8C8.2020506@utoronto.ca>

Dave Stubbs wrote:
> Niall Parker wrote:
> 
>> 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.
>>
> Got that one covered.  I'm redirecting all syslog messages, no matter 
> how insignificant or from what facility, to a central logging server 
> which puts them in a MySQL database.  From other programs running on the 
> same hambox as soundmodem, I'm getting so much information it's crazy, 
> so I don't think syslog is the problem in this case.  Is anyone else 
> using syslog to track soundmodem packets?
> 
> One other thought - maybe the trace that's coming up on my console is 
> not from the soundmodem software - maybe it's from kernel AX.25 code or 
> something?  Is there a way to redirect *that* to the syslog?
> 

Well,

I was able to confirm that.  I set my soundmodem to -v 0 and rebooted. 
The piddly little syslog trail vanished, but I still got the massive 
spew of all packets on the console.  I put the -v 9 back into soundmodem 
startup and the syslog messages started again (such as they are) and the 
console spew remains.

So, a new question - does anyone know where the console messages (they 
start with "Tx:") come from?  Can they be redirected to syslog or sent 
there instead of the console?

Thankyou,

Dave...
VA3BHF

  reply	other threads:[~2005-03-06 13:12 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
2005-03-06 12:34       ` Dave Stubbs
2005-03-06 13:12         ` Dave Stubbs [this message]
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=422B01BD.8030509@utoronto.ca \
    --to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).