Writing to System Logs Post: 302751245

Sponsored Content

Operating Systems Linux Red Hat Writing to System Logs Post 302751245 by thmnetwork on Thursday 3rd of January 2013 01:25:17 PM

01-03-2013

Registered User

How the date is formatted is decided by the syslog daemon which is in turn decided by how the daemon is configured. If the customer/clients wants that level of precision, they should reconfigure syslog to that it doesn't truncate the date like that. Doing something else might fix their problem with your application but still leaves that same level of ambiguity for all other logging going on with their system. So even they don't want to fix it another way. Just let them know that it's their syslog daemon that's doing the truncating and not your program.

Different distributions have different types of syslog daemons with sometimes slight differences so this is probably best left at a "You need to fix your syslog then" coming from your end. You can research the steps required for the various daemons and give them as helpful advice but I wouldn't really bother myself with more than that. Most of the popular syslog daemons (like rsyslog and syslog-ng) typically have some sort of "template" directive where the admin can specify the format and the fields they want to show up in their logs. Most daemons will also have an option for setting a default template, which is usually sufficient for making sure files show up in the new format (after a daemon reload).

I say usually because the admin could have some custom configuration going on where they've defined a particular format for the /var/log/maillog file or something. Which is another reason why you're in a better position to make suggestions to the admins rather than try to fix it yourself somehow.

Your solution does seem to be decent enough, but it's probably better for them to have the date on the same line as the message so they don't have to scrollback.

Last edited by thmnetwork; 01-03-2013 at 02:31 PM..

thmnetwork

View Public Profile for thmnetwork

Find all posts by thmnetwork

9 More Discussions You Might Find Interesting

1. Solaris

system logs' life

How can you control old system logs keep(or storage) time in Solaris ? Is there any method ? it depends on buffer size long or date long ?

2. Shell Programming and Scripting

not able to redirect the logs of a singl date in one system

Hi All, I have around 15 servers. I need to check for the error in /var/adm/messages in 15 servers of current date everyday and log it in one server. rsh is configured in all servers. The command I am using to accomplish this in shell script is rsh <remote sever> grep 'Jun 17'...

3. AIX

System Logs

Dear Gurus I am running AIX with several users that are using the system, i would like to monitor the commands that are run by these users. Is there a log system that records the commands that are executed by the users??? Any kind of help will be appreciated. Regards Masquerder

4. Shell Programming and Scripting

Grep yesterday logs from weblogic logs

Hi, I am trying to write a script which would go search and get the info from the logs based on yesterday timestamp and write yesterday logs in new file. The log file format is as follows: """"""""""""""""""""""""""...

5. Solaris

logs for system shutdown

I am working on a SUN T2000 machine with Solaris 10 running on it. When I checked the system this morning, I found it to be turned off. The lastreboot command showed that the system had been shut down the previous night. I want to find out how the system was shut down. I have run hardware health...

6. AIX

system logs

good evening all dear all where i can find the system logs in AIX 5.3

7. 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...

8. AIX

AIX system logs files

hello, i just want to know logs files for these actions listed below : - User Account Creation - User Account Deletion - Failed and or Successful User Password Changes - Failed Login Activities for all User Users - System Reboot or and shutdown help appreciated...

9. Shell Programming and Scripting

If I ran perl script again,old logs should move with today date and new logs should generate.

Appreciate help for the below issue. Im using below code.....I dont want to attach the logs when I ran the perl twice...I just want to take backup with today date and generate new logs...What I need to do for the below scirpt.............. 1)if logs exist it should move the logs with extention...

LEARN ABOUT OSF1

evmd

evmd(8) 						      System Manager's Manual							   evmd(8)

NAME

       evmd - Event Manager daemon

SYNOPSIS

       /usr/sbin/evmd

OPTIONS

       None

OPERANDS

       None

DESCRIPTION

       The  EVM  daemon,  evmd, receives events from posting clients and distributes them to subscribing clients that have indicated that they are
       interested in receiving them. The daemon is a critical system facility that is started automatically when the system transitions  to  level
       2, and which should not be terminated.  The daemon in turn starts the logger, evmlogger, and the channel manager, evmchmgr.

       On  startup,  the  daemon  reads its configuration file, /etc/evmdaemon.conf, the authorization file, /etc/evm.auth, and the event template
       files stored under the /usr/share/evm/templates directory.  If these files are modified while the daemon is running,  the  evmreload  -d(8)
       command must be used to instruct the daemon to reconfigure itself.

       The system administrator can control access to events at any level by modifying the EVM authorization file, /etc/evm.auth.

       As a daemon, evmd does not have a standard output. Any error messages are written to the file /var/evm/adm/logfiles/evmdaemon.log.

       The daemon reconfigures itself when evmreload -d is run, or upon receipt of a SIGHUP signal.

RESTRICTIONS

       The  daemon rejects any attempt by a posting client to post an event that is not registered, that contains invalid item values, or that the
       poster is not authorized to post.

EXIT VALUES

       The following exit values are returned: Successful completion An error occurred

FILES

       Executable file Default directory for event template files.  Default location for event filter files.  Filter files must  have  the  suffix
       .evf.   Error  log  file  for  evmd.   UNIX  domain socket established for connection between the EVM daemon and the local clients.  Daemon
       process id saved by evmd.  Lock file established to prevent multiple invocations of the daemon.	Default location of the EVM daemon config-
       uration file.  Default location of the EVM daemon authorization file.

SEE ALSO

       Commands: evmchmgr(8), evmd(8), evmlogger(8), evmreload(8), evmstart(8), evmstop(8)

       Files: evm.auth(4), evmdaemon.conf(4), evmtemplate(4)

       Event Management: EVM(5)

       Event Connection: EvmConnection(5)

       EVM Events: EvmEvent(5)

       Event Filter: EvmFilter(5)
       delim off

																	   evmd(8)