05-12-2018
So you have log management system, and you wonder how will you name logs that arrive at that central system ?
Stuff you posted are commands doing what a human or script instructed them on the box monitored.
Some of them read plain files, others inspect processes or follow links.
More or less standard stuff a user or administrator would do on a system, if allowed by permissions (files/directory permissions, ability to connect to machine etc.)
I'm not sure what kind of best practice advice you require.
Can you specify to more detail perhaps ?
And welcome to the forums
Regards
Peasant.
This User Gave Thanks to Peasant For This Post:
10 More Discussions You Might Find Interesting
1. IP Networking
I have a series of new machines that are internet facing (have IP's that are accessible via the 'net) and it has internal facing interfaces. I need to be able to communicate back to the internal network to a specific server which processes monitoring and e-mail traffic. I've been told that I should... (3 Replies)
Discussion started by: BOFH
3 Replies
2. UNIX for Dummies Questions & Answers
My goal was to find any directories inside of any directory called "09_Client Original" not modified in the last 30 days.
$ find /Volumes/Jobs_Volume/ -type d -name "09_Client Original" -exec find {} -mtime +30 -type d -maxdepth 1 \;
The results of this find are passed along in a perl script... (1 Reply)
Discussion started by: guriboy
1 Replies
3. UNIX for Advanced & Expert Users
Hello,
I'm wondering what is the naming conventions for *.so shared libraries in linux. For example, a library in /lib, say libcrypt-2.7.so has a symbolic link called libcrypt.so.1 pointing to it, yet libncursesw.so.5.6 has a symbolic link called libncursesw.so.5 pointing to it. What is the... (2 Replies)
Discussion started by: neked
2 Replies
4. Solaris
These are findings by me with my little experience with Solaris 10. Please correct me if wrong..
In x86 systems with ide hard disk:
c= controller
d=disk
s=slice
1.Here controller c0 means the primary ide controller ide0.
controller c1 means the secondary ide controller ide1.
... (5 Replies)
Discussion started by: saagar
5 Replies
5. UNIX for Dummies Questions & Answers
I would like to use an automated checker for adherence to CSS coding conventions. I have browsed the web, but no tool I came across checks for coding conventions, only syntax. Here is a general list of requirements:
- Style definitions should be separated by one blank line
- Indentation is 2... (0 Replies)
Discussion started by: figaro
0 Replies
6. UNIX for Dummies Questions & Answers
i was viewing the gawk's man file,checked the man faqs,didnt find anything about the char "e" meaning
.TP
.B \e`
matches the empty string at the beginning of a buffer (string).
.TP
.B \e'
matches the empty string at the end of a buffer.after convention,it should looks like thie
\` ... (2 Replies)
Discussion started by: b33713
2 Replies
7. Programming
C calling convention we all know defines a way how the parameters are pushed onto the stack.
My question is when and how does this C calling conventions matters to a user?
When the user will have to bother about the calling conventions in his project? (5 Replies)
Discussion started by: rupeshkp728
5 Replies
8. UNIX for Dummies Questions & Answers
is there a typographic convention that is followed in the man pages.
where could a description be found.
at this time i am in man stty and the author uses upper case in some places.
and my brain is just burning to a fizzle while studying a book on bash and trying to stay in scope of the... (1 Reply)
Discussion started by: cowLips
1 Replies
9. UNIX for Dummies Questions & Answers
I'm new to Unix, and just had a quick question.
I'm writing a bash script, and I was wondering what proper programming etiquette was for piping. How many pipes is too many pipes?
OLDEST=$(find . -maxdepth 1 -type d -newermt 2012-07-01 ! -newermt
2012-07-30 | xargs ls -1td | tail -2)
echo... (1 Reply)
Discussion started by: jrymer
1 Replies
10. Linux
I'm slowly hacking away at a zsh script that shows some promise as a command line tool. I want to learn more about the conventions regarding command line tool development in Unix (and/or macOS), but don't really know where to look for this information.
What is the correct way, or convention, to... (2 Replies)
Discussion started by: MonilGomes
2 Replies
log(8) System Manager's Manual log(8)
NAME
log - Records input and output from a program
SYNOPSIS
/usr/sbin/log <logfile> <command>
OPERANDS
The file in which to record the interaction being logged. The command to execute.
DESCRIPTION
The log program runs <command> and logs the input to and output from <command> to the <logfile> file. Input and output are logged until
<command> exits, the log program exits, and the exit status of <command> is returned.
The log program is used by the system installation procedure and the it(8) command to create the /var/adm/smlogs/install.log and
/var/adm/smlogs/it.log installation log files.
RESTRICTIONS
Because the log program is used in the installation standalone environment, program size was the greatest concern in its implementation.
The log program does not search for the PATH variable to locate <command> and error messages are terse.
The log program causes <command> to take standard input from and write standard output and standard error to UNIX pipes. Some commands
will not be able to operate in this environment; therefore, it is suggested that you use the script(1) command instead. UNIX shells will
not issue prompts when run from log unless the shell is started with an explicit interactive switch (-i for most shells). For example, log
foo.tmp /sbin/sh -i
In the previous example, foo.tmp is the name of <logfile>.
The log program intercepts end-of-file (usually Ctrl/d). Therefore programs which normally receive end-of-file as an exit command must
exit by some other means.
ERRORS
Log open error
Explanation:
The log program was unable to open <logfile>. Verify that the directory exists and that ownerships and permissions are set correctly.
Exec Error
Explanation:
The log program was unable to execute <command>. Verify that you specified a full pathname for <command> and that <command> is an exe-
cutable file.
Fork Error
Explanation:
The log program was unable to create one of the processes it requires to log data.
SEE ALSO
Commands: it(8), script(1)
log(8)