Sponsored Content
Top Forums UNIX for Dummies Questions & Answers How to write code for a Logging Event? Post 302579436 by Corona688 on Monday 5th of December 2011 05:38:48 PM
Old 12-05-2011
Still think you're overthinking this. It can be as simple as using stdout and stderr:

Code:
printf("handling event...\n"); //stdout

if(error)
{
        fprintf(stderr, "Something we couldn't fix happened!  Error %d\n", 32); // stderr
        exit(1);
}

Code:
./myapplication > /path/to/access.log 2> /path/to/error.log

Or if you want you can use syslog (see man 3 syslog) :

Code:
#include <syslog.h>
#include <stdarg.h>


...

openlog("myprogram", LOG_PID, LOG_DAEMON);

...

syslog(LOG_DEBUG, "Hello, something happened!  Error %d", 32);
exit(1);

Though you can no longer control what file it goes into from your appplication, that's up to the system logger.
 

5 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

How does Unix write events into event log?

Hi to everyone. I'm new to this forum and also pretty new to Unix. I'm developing a cross-platform software and I need to register informational and error messages into the event log of the system. Under Windows, this is implemented so far, I need to implement it unded Unix by now. I do know that... (7 Replies)
Discussion started by: mariano_donati
7 Replies

2. IP Networking

read/write,write/write lock with smbclient fails

Hi, We have smb client running on two of the linux boxes and smb server on another linux system. During a backup operation which uses smb, read of a file was allowed while write to the same file was going on.Also simultaneous writes to the same file were allowed.Following are the settings in the... (1 Reply)
Discussion started by: swatidas11
1 Replies

3. Shell Programming and Scripting

Event logging to file and display to console | tee command is not able to log all info.

My intention is to log the output to a file as well as it should be displayed on the console > I have used tee ( tee -a ${filename} ) command for this purpose. This is working as expected for first few outputs, after some event loggin nothing is gettting logged in to the file but It is displaying... (3 Replies)
Discussion started by: sanoop
3 Replies

4. Shell Programming and Scripting

Logging success event into file

Hi, I've the following code to log the errors any after the command is executed. # Ksh 88 Version log_path=/home/etc/fls/fls_log.log del_path=/home/etc/fls/to_day rm $del_path/* >> $log_path 2>&1 But I even want to log if the rm command is success without any error along with... (1 Reply)
Discussion started by: smile689
1 Replies

5. Linux

Syslog not logging successful logging while unlocking server's console

When unlocking a Linux server's console there's no event indicating successful logging Is there a way I can fix this ? I have the following in my rsyslog.conf auth.info /var/log/secure authpriv.info /var/log/secure (1 Reply)
Discussion started by: walterthered
1 Replies
SYSLOG(3)						     Linux Programmer's Manual							 SYSLOG(3)

NAME
closelog, openlog, syslog - send messages to the system logger SYNOPSIS
#include <syslog.h> void openlog(const char *ident, int option, int facility); void syslog(int priority, const char *format, ...); void closelog(void); #include <stdarg.h> void vsyslog(int priority, const char *format, va_list ap); DESCRIPTION
closelog() closes the descriptor being used to write to the system logger. The use of closelog() is optional. openlog() opens a connection to the system logger for a program. The string pointed to by ident is prepended to every message, and is typ- ically set to the program name. The option argument specifies flags which control the operation of openlog() and subsequent calls to sys- log(). The facility argument establishes a default to be used if none is specified in subsequent calls to syslog(). Values for option and facility are given below. The use of openlog() is optional; it will automatically be called by syslog() if necessary, in which case ident will default to NULL. syslog() generates a log message, which will be distributed by syslogd(8). The priority argument is formed by ORing the facility and the level values (explained below). The remaining arguments are a format, as in printf(3) and any arguments required by the format, except that the two character sequence %m will be replaced by the error message string strerror(errno). A trailing newline is added when needed. The function vsyslog() performs the same task as syslog() with the difference that it takes a set of arguments which have been obtained using the stdarg(3) variable argument list macros. PARAMETERS
This section lists the parameters used to set the values of option, facility, and priority. option The option argument to openlog() is an OR of any of these: LOG_CONS Write directly to system console if there is an error while sending to system logger. LOG_NDELAY Open the connection immediately (normally, the connection is opened when the first message is logged). LOG_NOWAIT Don't wait for child processes that may have been created while logging the message. (The GNU C library does not create a child process, so this option has no effect on Linux.) LOG_ODELAY The converse of LOG_NDELAY; opening of the connection is delayed until syslog() is called. (This is the default, and need not be specified.) LOG_PERROR (Not in SUSv3.) Print to stderr as well. LOG_PID Include PID with each message. facility The facility argument is used to specify what type of program is logging the message. This lets the configuration file specify that mes- sages from different facilities will be handled differently. LOG_AUTH security/authorization messages (DEPRECATED Use LOG_AUTHPRIV instead) LOG_AUTHPRIV security/authorization messages (private) LOG_CRON clock daemon (cron and at) LOG_DAEMON system daemons without separate facility value LOG_FTP ftp daemon LOG_KERN kernel messages LOG_LOCAL0 through LOG_LOCAL7 reserved for local use LOG_LPR line printer subsystem LOG_MAIL mail subsystem LOG_NEWS USENET news subsystem LOG_SYSLOG messages generated internally by syslogd LOG_USER (default) generic user-level messages LOG_UUCP UUCP subsystem level This determines the importance of the message. The levels are, in order of decreasing importance: LOG_EMERG system is unusable LOG_ALERT action must be taken immediately LOG_CRIT critical conditions LOG_ERR error conditions LOG_WARNING warning conditions LOG_NOTICE normal, but significant, condition LOG_INFO informational message LOG_DEBUG debug-level message The function setlogmask(3) can be used to restrict logging to specified levels only. CONFORMING TO
The functions openlog(), closelog(), and syslog() (but not vsyslog()) are specified in SUSv2 and POSIX 1003.1-2001. POSIX 1003.1-2001 specifies only the LOG_USER and LOG_LOCAL* values for facility. However, with the exception of LOG_AUTHPRIV and LOG_FTP, the other facil- ity values appear on most Unix systems. The LOG_PERROR value for option is not specified by POSIX 1003.1-2001, but is available in most versions of Unix. HISTORY
A syslog function call appeared in BSD 4.2. BSD 4.3 documents openlog(), syslog(), closelog(), and setlogmask(). 4.3BSD-Reno also docu- ments vsyslog(). Of course early v* functions used the <varargs.h> mechanism, which is not compatible with <stdarg.h>. NOTES
The parameter ident in the call of openlog() is probably stored as-is. Thus, if the string it points to is changed, syslog() may start prepending the changed string, and if the string it points to ceases to exist, the results are undefined. Most portable is to use a string constant. Never pass a string with user-supplied data as a format, use syslog("%s", string); instead. SEE ALSO
logger(1), setlogmask(3), syslog.conf(5), syslogd(8) Linux 2002-01-03 SYSLOG(3)
All times are GMT -4. The time now is 09:09 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy