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?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.
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?
Dave... - To unsubscribe from this list: send the line "unsubscribe linux-hams" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
