Sponsored Content
Top Forums Programming why I can't get syslog message? Post 302252615 by konvalo on Thursday 30th of October 2008 12:58:35 AM
Old 10-30-2008
Question why I can't get syslog message?

I read Unix network programming by richard,in chap12.3,it say if call syslog() by using parameter LOG_USER,it should write a message in /var/adm/messages in Solaris,such as "connected from 10.1.1.2",example file inet/daytimetcpsrv2.c.I want to know which syslog file in FreeBSD7.0?I look for /var/log/messages,I don't find my message "connected from 10.1.1.2" in this file. Why?

My syslog.conf is follows:
Quote:
# $FreeBSD: src/etc/syslog.conf,v 1.28 2005/03/12 12:31:16 glebius Exp $
#
# Spaces ARE valid field separators in this file. However,
# other *nix-like systems still insist on using tabs as field
# separators. If you are sharing this file between systems, you
# may want to use only tabs as field separators here.
# Consult the syslog.conf(5) manpage.
*.err;kern.warning;auth.notice;mail.crit /dev/console
*.notice;authpriv.none;kern.debug;lpr.info;mail.crit;news.err /var/log/messages
security.* /var/log/security
auth.info;authpriv.info /var/log/auth.log
mail.info /var/log/maillog
lpr.info /var/log/lpd-errs
ftp.info /var/log/xferlog
cron.* /var/log/cron
*.=debug /var/log/debug.log
*.emerg *
# uncomment this to log all writes to /dev/console to /var/log/console.log
#console.info /var/log/console.log
# uncomment this to enable logging of all log messages to /var/log/all.log
# touch /var/log/all.log and chmod it to mode 600 before it will work
#*.* /var/log/all.log
# uncomment this to enable logging to a remote loghost named loghost
#*.* @loghost
# uncomment these if you're running inn
# news.crit /var/log/news/news.crit
# news.err /var/log/news/news.err
# news.notice /var/log/news/news.notice
!startslip
*.* /var/log/slip.log
!ppp
*.* /var/log/ppp.log

Last edited by Neo; 04-01-2012 at 02:08 PM.. Reason: quote tags or code tags, please!
 

10 More Discussions You Might Find Interesting

1. Solaris

syslog message..!

I got my system sun fire 6800 hung later reboot after generating these message can any one help me on this to review these message..!! nfssrv: WARNING: nfsauth upcall failed: RPC: Operation in progress mountd: cannot accept connection: 19: error unknown (current state -1) KAVE00166-W The... (13 Replies)
Discussion started by: nicknihal
13 Replies

2. Programming

How to limit max no of message in a posix message queue

Hii can anyone pls tell how to limit the max no of message in a posix message queue. I have made changes in proc/sys/fs/mqueue/msg_max But still whenever i try to read the value of max. message in the queue using attr.mq_curmsgs (where struct mq_attr attr) its giving the default value as 10.... (0 Replies)
Discussion started by: mohit3884
0 Replies

3. AIX

Syslog - Message forwarded from

I am not a Unix / AIX admin, but am working with one that doesn't seem to know how to set up syslog to forward messages to me the way I need them. Every message they send me has "Message forwarded from <insert host name here>:" but I need it to only have the host name. In the examples below,... (2 Replies)
Discussion started by: mlbillow
2 Replies

4. UNIX for Advanced & Expert Users

Q on <user> of syslog message generated by logger command

Generally(at least on AIX5.3, Solaris9, OS X)'logger' command would create syslog messages which carry <login name> . On Solaris9, I have experienced two circumstances in which 'logname' command fails. In this circumstance I saw the 'logger' command generated syslog messages which carry... (0 Replies)
Discussion started by: masaki
0 Replies

5. UNIX for Dummies Questions & Answers

Syslog Message Columns

Hi all, I need your help with syslog columns. Currently I have a script as follows: (extract) for messages in `cat syslog_message_list.txt`; \ do \ grep $messages syslog.`date +%d%m%y`.log | \ tr -s " " | \ cut -d" " -f4,9- | \ sort -k3.2,3 -k2,2 -k1nr,1 | \ uniq -c | \ sort -k3.2,3... (6 Replies)
Discussion started by: wthomas
6 Replies

6. Red Hat

Syslog Message

All thanks for the help in advance. I'm current have my syslog server built on RHEL5.7. I'm wondering how to I have the syslog messages categorized by hostname? Is that an option I can add to the syslog.conf? (1 Reply)
Discussion started by: aojmoj
1 Replies

7. UNIX and Linux Applications

Ssmtp -t < /path/to/the/message.txt (How to format message.txt for html email)

ssmtp has been running well under Kubuntu 12.04.1 for plain text messages. I would like to send html messages with ssmtp -t < /path/to/the/message.txt, but I cannot seem to get the message.txt file properly formatted. I have tried various charsets, Content-Transfer-Encoding, rearranging the... (0 Replies)
Discussion started by: Ronald B
0 Replies

8. AIX

Message redirected from syslog

Hi. recently in many of our lpars we are getting a message in errpt as "C6ACA566 0315094014 U S dtc MESSAGE REDIRECTED FROM SYSLOG". I have also checked the /etc/syslog.conf file. It doesn't point to error log. Can someone please advise about how to fix this error ? pmut3:/> errpt -aj... (4 Replies)
Discussion started by: newtoaixos
4 Replies

9. HP-UX

Generate message in syslog.log

Dear Concern, Is there any command to generate message in /var/adm/syslog/syslog.log file in HP-UX. With Best Regards, Kauser (2 Replies)
Discussion started by: makauser
2 Replies

10. Ubuntu

How redirect syslog message to a specified file?

Hello to everyone! I have a question about syslog. I want put the messages of log in a particular file but really i don't know how to do that or i don't get the results that I want. I do this: #include <stdio.h> #include <stdlib.h> #include <syslog.h> int main (void) { ... (4 Replies)
Discussion started by: Kovalevski
4 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 Operating 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 possible 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 net- work. 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. FILES
/var/log/notice log of all mail system messages (except debug messages) and all messages of notice level or higher /var/log/critical log of all critical messages /var/log/auth log of all messages from the authorization system of warning level or higher 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.10 28 Jul 2004 syslog.conf(4)
All times are GMT -4. The time now is 06:26 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy