Sponsored Content
Top Forums UNIX for Advanced & Expert Users Is it, and if so, how is it possible to intercept system messages going to SYSLOG Post 302301112 by bennerg on Thursday 26th of March 2009 02:13:39 AM
Old 03-26-2009
Is it, and if so, how is it possible to intercept system messages going to SYSLOG

HI all,

I'm trying to improve my systems to detect attempts to break in to my servers. For instance, I currently use crontab checking the /var/log/messages every 1 minute, but I feel it would be more efficient to do the processing only when messages are generated.

Is this possible, and if so how?

kr
gary
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

system messages log (Sun and AIX)

Hello, I need a few explanation about the log files for system messages: /var/adm/messages and /var/log/syslog. As /var/adm/messages is empty on my machine, i need help. First, i would like to know what the difference between these 2 files is? Do they contain different kinds of system... (3 Replies)
Discussion started by: VeroL
3 Replies

2. UNIX for Advanced & Expert Users

System Error messages

Hi Experts, I'm getting the following errors on /var/adm/messages file permanently. Dec 28 10:19:38 ioocsrv1 bsd-gw: open(dfA415ioocsrv3): File exists Dec 28 10:20:53 ioocsrv1 bsd-gw: open(dfA415ioocsrv3): File exists Dec 28 10:22:08 ioocsrv1 bsd-gw: open(dfA415ioocsrv3): File exists Dec... (1 Reply)
Discussion started by: nikk
1 Replies

3. IP Networking

intercept the ip address of a telnet session

The situation: a Unix system (UnixWare 7.1.3) to which are connected other systems; various p.c. on the LAN that they connect Unix to the system via TelNet. The problem: I need to intercept the address IP of the p.cs. connected via telnet to the Unix system. Particularly, I have to know the... (2 Replies)
Discussion started by: paololrp
2 Replies

4. Shell Programming and Scripting

Script to send something via UDP and intercept at other end?

I am looking to do a shell script that can send something simple via UDP from server 1 - to server 2 I want to be able to see on server 2 that I received everything expected.. ie.. I am looking at this to avoid using ping / traceroute to highlight network issues.. if a UDP packet gets lost... (1 Reply)
Discussion started by: frustrated1
1 Replies

5. AIX

How to intercept sytem calls

I would like to port a small utility from Linux to AIX and, lacking any software development knowledge for AIX, need some help: I have a library called Snoopy. Basically it intercepts the execv() and execve() system calls and logs them to the syslog-facility AUTHPRIV then passes control over to... (1 Reply)
Discussion started by: bakunin
1 Replies

6. Red Hat

syslog messages.

Good Day. Any idea on the messages log. it would be a great help to us. Upon checking the on the system logs, I found the following messages: EXT3-fs: INFO: recovery required on readonly filesystem. EXT3-fs: write access will be enabled during recovery. kjournald... (1 Reply)
Discussion started by: cabloy
1 Replies

7. UNIX for Advanced & Expert Users

Video Cards :: Video Memory Intercept and Redirect

I need a broad spectrum understanding on this subject, and any help would be greatly appreciated. First of all, as I understand it... The way the video hardware works is the CPU sends information about input and possible changes to the display, the video card receives these changes, makes the... (2 Replies)
Discussion started by: ciNG
2 Replies

8. Homework & Coursework Questions

program to send messages to parent using pipes and select system call

Write a program using select, which will create some number of child processes that continuously send text messages to the parent process using pipes. Each child has its own pipe that it uses to communicate with the parent. The parent uses select () to decide what pipes should be processed to... (1 Reply)
Discussion started by: ripssingh
1 Replies

9. UNIX for Advanced & Expert Users

Scan all mail messages through the server and save a copy into file system following a rule

In our company we work for our customer with a job# philosophy, managing all the informations about a job in a share with directories whose name is starting with job number. Under this entry point we have a standard structure of folders, comprising a "communications" folder. When we send emails... (0 Replies)
Discussion started by: vroby67
0 Replies

10. Solaris

Svc messages flooding the system logs every second

Hi all I have a newly installed Oracle X2-4 server running Solaris 10 x86 with the latest patches. I have one non-global zone configured running an Oracle DB instance. After configuring IPMP failover between two NICs on the server and rebooting I am seeing the /var/adm/messages being flooded... (7 Replies)
Discussion started by: notreallyhere
7 Replies
syslog.conf(4)							   File Formats 						    syslog.conf(4)

NAME
syslog.conf - configuration file for syslogd system log daemon SYNOPSIS
/etc/syslog.conf DESCRIPTION
The file /etc/syslog.conf contains information used by the system log daemon, syslogd(1M), to forward a system message to appropriate log files and/or users. syslogd preprocesses this file through m4(1) to obtain the correct information for certain log files, defining LOGHOST if the address of "loghost" is the same as one of the addresses of the host that is running syslogd. A configuration entry is composed of two TAB-separated fields: selector action The selector field contains a semicolon-separated list of priority specifications of the form: facility.level [ ; facility.level ] where facility is a system facility, or comma-separated list of facilities, and level is an indication of the severity of the condition being logged. Recognized values for facility include: user Messages generated by user processes. This is the default priority for messages from programs or facilities not listed in this file. kern Messages generated by the kernel. mail The mail system. daemon System daemons, such as in.ftpd(1M) auth The authorization system: login(1), su(1M), getty(1M), among others. lpr The line printer spooling system: lpr(1B), lpc(1B), among others. news Designated for the USENET network news system. uucp Designated for the UUCP system; it does not currently use the syslog mechanism. cron Designated for cron/at messages generated by systems that do logging through syslog. The current version of the Solaris Operat- ing Environment does not use this facility for logging. audit Designated for audit messages generated by systems that audit by means of syslog. local0-7 Designated for local use. mark For timestamp messages produced internally by syslogd. * An asterisk indicates all facilities except for the mark facility. Recognized values for level are (in descending order of severity): emerg For panic conditions that would normally be broadcast to all users. alert For conditions that should be corrected immediately, such as a corrupted system database. crit For warnings about critical conditions, such as hard device errors. err For other errors. warning For warning messages. notice For conditions that are not error conditions, but may require special handling. A configuration entry with a level value of notice must appear on a separate line. info Informational messages. debug For messages that are normally used only when debugging a program. none Do not send messages from the indicated facility to the selected file. For example, a selector of *.debug;mail.none sends all messages except mail messages to the selected file. For a given facility and level, syslogd matches all messages for that level and all higher levels. For example, an entry that specifies a level of crit also logs messages at the alert and emerg levels. The action field indicates where to forward the message. Values for this field can have one of four forms: o A filename, beginning with a leading slash, which indicates that messages specified by the selector are to be written to the specified file. The file is opened in append mode if it exists. If the file does not exist, logging silently fails for this action. o The name of a remote host, prefixed with an @, as with: @server, which indicates that messages specified by the selector are to be forwarded to the syslogd on the named host. The hostname "loghost" is treated, in the default syslog.conf, as the hostname given to the machine that logs syslogd messages. Every machine is "loghost" by default, per the hosts database. It is also pos- sible to specify one machine on a network to be "loghost" by, literally, naming the machine "loghost". If the local machine is designated to be "loghost", then syslogd messages are written to the appropriate files. Otherwise, they are sent to the machine "loghost" on the network. o A comma-separated list of usernames, which indicates that messages specified by the selector are to be written to the named users if they are logged in. o An asterisk, which indicates that messages specified by the selector are to be written to all logged-in users. Blank lines are ignored. Lines for which the first nonwhite character is a '#' are treated as comments. EXAMPLES
Example 1 A Sample Configuration File With the following configuration file: *.notice /var/log/notice mail.info /var/log/notice *.crit /var/log/critical kern,mark.debug /dev/console kern.err @server *.emerg * *.alert root,operator *.alert;auth.warning /var/log/auth syslogd(1M) logs all mail system messages except debug messages and all notice (or higher) messages into a file named /var/log/notice. It logs all critical messages into /var/log/critical, and all kernel messages and 20-minute marks onto the system console. Kernel messages of err (error) severity or higher are forwarded to the machine named server. Emergency messages are forwarded to all users. The users root and operator are informed of any alert messages. All messages from the authorization system of warning level or higher are logged in the file /var/log/auth. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface Stability |Stable | +-----------------------------+-----------------------------+ SEE ALSO
at(1), crontab(1), logger(1), login(1), lp(1), lpc(1B), lpr(1B), m4(1), cron(1M), getty(1M), in.ftpd(1M), su(1M), syslogd(1M), syslog(3C), hosts(4), attributes(5) SunOS 5.11 26 Apr 2006 syslog.conf(4)
All times are GMT -4. The time now is 12:53 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy