Sponsored Content
Top Forums UNIX for Dummies Questions & Answers How to write code for a Logging Event? Post 302580144 by Corona688 on Wednesday 7th of December 2011 04:36:43 PM
Old 12-07-2011
You're really overthinking this. It's like looking for a specification designed to print the letter 'A', and because there's no specifications specifically about printing the letter 'A', deciding that printing the letter 'A' is something very mysterious, complicated, and badly documented.

You can either write error messages to stderr, write them to a file, or use the system logger. Shell utilities usually use stderr. System daemons usually use files or the system logger. What an 'error' is, and what deserves logging, is up to you. syslog in particular lets you tell it how important the message is when you make it.

What's more useful to know is how other things return errors. See man errno, the global variable many things set on error. There's also a set of functions to use with it. Also see man 3 syslog for the "standard" way errors are recorded on a UNIX system -- it's not just a library call, there's log-related parts of the kernel it talks to.

Last edited by Corona688; 12-07-2011 at 05:45 PM..
This User Gave Thanks to Corona688 For This Post:
 

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
PERROR(3)						     Linux Programmer's Manual							 PERROR(3)

NAME
perror - print a system error message SYNOPSIS
#include <stdio.h> void perror(const char *s); #include <errno.h> const char *sys_errlist[]; int sys_nerr; int errno; Feature Test Macro Requirements for glibc (see feature_test_macros(7)): sys_errlist, sys_nerr: _BSD_SOURCE DESCRIPTION
The routine perror() produces a message on the standard error output, describing the last error encountered during a call to a system or library function. First (if s is not NULL and *s is not a null byte ('')) the argument string s is printed, followed by a colon and a blank. Then the message and a new-line. To be of most use, the argument string should include the name of the function that incurred the error. The error number is taken from the external variable errno, which is set when errors occur but not cleared when successful calls are made. The global error list sys_errlist[] indexed by errno can be used to obtain the error message without the newline. The largest message num- ber provided in the table is sys_nerr-1. Be careful when directly accessing this list because new error values may not have been added to sys_errlist[]. The use of sys_errlist[] is nowadays deprecated. When a system call fails, it usually returns -1 and sets the variable errno to a value describing what went wrong. (These values can be found in <errno.h>.) Many library functions do likewise. The function perror() serves to translate this error code into human-readable form. Note that errno is undefined after a successful library call: this call may well change this variable, even though it succeeds, for example because it internally used some other library function that failed. Thus, if a failing call is not immediately followed by a call to perror(), the value of errno should be saved. CONFORMING TO
The function perror() and the external errno (see errno(3)) conform to C89, C99, 4.3BSD, POSIX.1-2001. The externals sys_nerr and sys_errlist conform to BSD. NOTES
The externals sys_nerr and sys_errlist are defined by glibc, but in <stdio.h>. SEE ALSO
err(3), errno(3), error(3), strerror(3) COLOPHON
This page is part of release 3.53 of the Linux man-pages project. A description of the project, and information about reporting bugs, can be found at http://www.kernel.org/doc/man-pages/. 2012-04-17 PERROR(3)
All times are GMT -4. The time now is 10:43 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy