The modular syslog allows for an easy implementation of input and output modules. The modules that mantain compatibility with its precursor are included in the standard distribution along with four modules: om_peo (an implementation of PEO-1 and L-PEO, two algorithmic protocols for integrity checking), om_mysql and om_pgsql (modules that sends output to a mysql and postgresql database, respectively) and om_regex (a module that allows output redirection using regular expressions).
| Tags | Logging Security Cryptography |
|---|---|
| Licenses | BSD Original |
| Operating Systems | POSIX AIX BSD OpenBSD IRIX Linux Solaris |
| Implementation | C |
Recent releases


Release Notes: This release compiles well on *BSD. New modules should be used with caution.


Release Notes: This version includes some module work and plenty of bugfixes.


Release Notes: MySQL manpage typos were fixed. Debugging info is now printed when INSERT doesn't work on MySQL. A new im_file module was added, which reads from files and pipes. The library no longer needs global variables. Split line bugs were fixed. An option for using local host names with a domain was added.


Release Notes: The name of the pidfile was fixed to suit scripts for sysklogd. Minor improvements were made to the manpages.


Release Notes: Fixes for some compilation problems and errors managing host names.
Recent comments
15 Mar 2005 01:33
query: msyslog
hai,
i have installed msyslog in my system but i am not able to log messages. i am not able to understand of how to use msyslog. can u please help me in configuring msyslog.
please send me the instructions of how to use msyslog.
waiting for ur reply
sai.
mailid: saireddyt@yahoo.com
11 Sep 2003 20:21
Re: I can't get msyslog to dump to mysql database
I followed all the step to set up msyslog. I can't get it to log to mysql database. I think it has to do with om_mysql. Here's my log. I also made sure I have libmysqlclient. Can anyone help??
Sep 11 17:38:58 scanman msyslog: msyslogd shutdown succeeded
Sep 11 19:13:51 scanman sshd(pam_unix)[25553]: session opened for user root by (uid=0)
Sep 11 19:15:42 scanman sshd(pam_unix)[25553]: session opened for user root by (uid=0)
Sep 11 19:25:32 scanman syslogd: exiting on signal 1
Sep 11 19:25:33 scanman.okstate.edu syslogd: restart
Sep 11 19:25:33 scanman.okstate.edu msyslogd: syslogd: WARNING error on input module, ignoring om_mysql
Sep 11 19:25:33 scanman.okstate.edu msyslog: msyslogd startup succeeded
Sep 11 19:25:33 scanman.okstate.edu msyslog: msyslogd shutdown succeeded
Sep 11 19:13:51 scanman sshd[25553]: Accepted password for root from 10.120.1.114 port 2404 ssh2
17 Jul 2003 18:14
Re: msyslog rocks!
> I've been using modular syslog to backup
> all of the logs from all of my servers
> to a secure site. This tool makes
> watching all of the syslogs from my
> servers a very easy task! This project
> is great and deserves some praise!
> Cheers!
>
> Jaa Matane,
>
> Dylan
I wonder if u could give me some detail config about
msyslog. eg. mysql.msyslog.conf.etc...
12 Jan 2003 23:07
I prefer syslog-ng for SQL
I found this project trying to find a way to direct
syslog messages to an SQL database. For me,
msyslog was frustrating to configure and use.
Then I found syslog-ng and I was able to get it
working with little hassle. Directing to a SQL
database is as easy as writing a script to read a
pipe and have syslog direct messages to a pipe.
See the syslog documentation about the pipe
destination and use the template option.
20 Sep 2002 07:32
Re: msyslog not logging to MySQL Database
"ln -s libmysqlclient.so mysql/libmysqlclient.so"
in /usr/lib to solve this problem...