Sponsored Content
Full Discussion: HPUX syslog configuration
Operating Systems HP-UX HPUX syslog configuration Post 302936634 by sembii on Thursday 26th of February 2015 10:25:23 PM
Old 02-26-2015
HPUX syslog configuration

Hi all,

We have few HPUX servers. Our monitoring server collects their CPU usage info, memory info and disk info in 5 min time interval.
Now, problem is massive access log from monitoring server logged in syslog.log on all hpux servers.

How can we prevent these access logs to be logged from particular host. Do I need to write script that does some search and delete action from log file? Or is there any other option?

Thanks
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

HPUX 10.20 et HPUX 11

Is there any problems of binaries compatibility between HPUX 10.20 et 11 ? (2 Replies)
Discussion started by: Olivier
2 Replies

2. Linux

syslog configuration

Hi I have redhat linux v9.x. This is acting as a syslog server. I have a 1700 series cisco router I would like to log all the activity of my cisco router on my syslog server. Please anyone help me to configure it Regards, Raja (0 Replies)
Discussion started by: RajaRC
0 Replies

3. HP-UX

HPUX any help

:( i got couple of weeks ago a : HP Visualize workstation , model B100. everithing is ok in the box the only problem is that i 'am not familiar with this operational sys, and i try to uninstall and see if i can get on it windows net server 64 bit. or any other 64 bit operational sys that i'll... (1 Reply)
Discussion started by: newbird
1 Replies

4. UNIX for Dummies Questions & Answers

Configuration of email on HPUX server

I am working in an developer 2000 based application where backend is Oracle9i in unix environment. My application has the functionality if email generation. But I am not able to test this functionality as my HPUX server is not configured for emails. Please let me know the steps for configuring mail... (1 Reply)
Discussion started by: sharmavr
1 Replies

5. Shell Programming and Scripting

Need Script to Use CPUs on a HPUX server to simulate Workload Manager on HPUX.

I am running HPUX and using WLM (workload manager). I want to write a script to fork CPUs to basically take CPUs from other servers to show that the communication is working and CPU licensing is working. Basically, I want to build a script that will use up CPU on a server. Any ideas? (2 Replies)
Discussion started by: cpolikowsky
2 Replies

6. Shell Programming and Scripting

hpux vi

Hello. I cant figure out how can i move entire row up , so it pasted on the one above at the end , or to do that for one character. In notepads,word, or some other text editors we would do that with backspace button. Example. Content of my text file is this : I am trying to do that. And... (2 Replies)
Discussion started by: tonijel
2 Replies

7. Red Hat

syslog configuration and log lvl

Hello I was getting hammered in /var/log/messages from snmpd becouse it was running a jira which was sending email everytime someone updated a case or made any changes. Therefor I decided to turn down the loglvl of snmpd, so what I did was add snmpd.notice; to # cat /etc/syslog.conf # Log... (2 Replies)
Discussion started by: chipmunken
2 Replies

8. HP-UX

pwage-hpux-T for Trusted HPUX servers

I'm sharing this in case anybody needs it. Modified from the original solaris pwage script. This modified hpux script will check /etc/password file on hpux trusted systems search /tcb and grep the required u_succhg field. Calculate days to expiry and notify users via email. original solaris... (2 Replies)
Discussion started by: sparcguy
2 Replies

9. Solaris

best configuration for syslog.conf

I would like to configure the syslog.conf to have a good monitoring information about my system. do you have any idea about best configuration from your experience in your Data Centers BR, (5 Replies)
Discussion started by: maxim42
5 Replies

10. Shell Programming and Scripting

Hpux

Hello All Why is hpux is not much spoken in the unix/Linux platform. what is the disadvantes in HPUX Thanks, VJ (1 Reply)
Discussion started by: Vijaykannan T
1 Replies
LOG(1)							User Contributed Perl Documentation						    LOG(1)

NAME
Apache::Log -- Perl API for Apache Logging Methods Synopsis #in startup.pl #------------- use Apache::Log; my $s = Apache->server; $s->log_error("server: log_error"); $s->log_serror(Apache::LOG_MARK, Apache::LOG_ERR, 0, "log_serror logging at err level"); $s->log_serror(Apache::LOG_MARK, Apache::LOG_DEBUG, APR::ENOTIME, "debug print"); Apache::Server->log_error("routine warning"); Apache->warn("routine warning"); Apache::warn("routine warning"); Apache::Server->warn("routine warning"); #in a handler #------------ use Apache::Log; sub handler{ my $r = shift; $r->log_error("request: log_error"); $r->warn("whoah!"); my $rlog = $r->log; for my $level qw(emerg alert crit error warn notice info debug) { no strict 'refs'; $rlog->$level($package, "request: $level log level"); } # can use server methods as well my $s = $r->server; $s->log_error("server: log_error"); $r->log_rerror(Apache::LOG_MARK, Apache::LOG_DEBUG, APR::ENOTIME, "in debug"); $s->log_serror(Apache::LOG_MARK, Apache::LOG_INFO, 0, "server info"); $s->log_serror(Apache::LOG_MARK, Apache::LOG_ERR, APR::ENOTIME, "fatal error"); $s->warn('routine server warning'); } Description "Apache::Log" provides the Perl API for Apache logging methods. Constants The following constants (sorted from the most severe level to the least severe) are used in logging methods to specify the log level at which the message should be logged: o "Apache::LOG_EMERG" o "Apache::LOG_ALERT" o "Apache::LOG_CRIT" o "Apache::LOG_ERR" o "Apache::LOG_WARNING" o "Apache::LOG_NOTICE" o "Apache::LOG_INFO" o "Apache::LOG_DEBUG" For example if the current "LogLevel" is set to warning, only messages with log level of the level warning or higher (err, crit, elert and emerg) will be logged. Therefore this: $r->log_rerror(Apache::LOG_MARK, Apache::LOG_WARNING, APR::ENOTIME, "warning!"); will log the message, but this one won't: $r->log_rerror(Apache::LOG_MARK, Apache::LOG_INFO, APR::ENOTIME, "just an info"); It will be logged only if the server log level is set to info or debug. (either in the configuration file or using the "$s->loglevel()" method.) Other constants: o "Apache::LOG_LEVELMASK" used to mask off the level value, to make sure that the log level's value is within the proper bits range. e.g.: $loglevel &= LOG_LEVELMASK; o "Apache::LOG_TOCLIENT" used to give content handlers the option of including the error text in the "ErrorDocument" sent back to the client. When "Apache::LOG_TOCLIENT" is passed to "log_rerror()" the error message will be saved in the $r's notes table, keyed to the string "error-notes", if and only if the severity level of the message is "Apache::LOG_WARNING" or greater and there are no other "error-notes" entry already set in the request record's notes table. Once the "error-notes" entry is set, it is up to the error handler to determine whether this text should be sent back to the client. For example: $r->log_rerror(Apache::LOG_MARK, Apache::LOG_ERR|Apache::LOG_TOCLIENT, APR::ENOTIME, "request log_rerror"); now the log message can be retrieved via: $r->notes->get("error-notes"); Remember that client generated text streams sent back to the client MUST be escaped to prevent CSS attacks. o "Apache::LOG_STARTUP" is set only during the startup. Server Logging Methods "$s->log_error()" $s->log_error(@message); just logs the supplied message. For example: $s->log_error("running low on memory"); "$s->log_serror()" log_serror($file, $line, $level, $status, @message); where: * $file The file in which this function is called * $line The line number on which this function is called * $level The level of this error message * $status The status code from the previous command * @message The log message This function provides a fine control of when the message is logged, gives an access to built-in status codes. For example: $s->log_serror(Apache::LOG_MARK, Apache::LOG_ERR, 0, "log_serror logging at err level"); $s->log_serror(Apache::LOG_MARK, Apache::LOG_DEBUG, APR::ENOTIME, "debug print"); "$s->log()" my $slog = $s->log; returns a handle which can be used to log messages of different level. See the next entry. emerg(), alert(), crit(), error(), warn(), notice(), info(), debug() $s->log->emerg(@message); after getting the log handle with "$s->log", use these methods to control when messages should be logged. For example: my $slog = $s->log; $slog->debug("just ", "some debug info"); $slog->warn(@warnings); $slog->crit("dying"); Request Logging Methods "$r->log_error()" $r->log_error(@message); logs the supplied message (similar to "$s->log_error"). For example: $r->log_error("the request is about to end"); the same as "$s->log_error". "$r->log_rerror()" log_rerror($file, $line, $level, $status, @message); same as "$s->log_rerror". For example: $s->log_rerror(Apache::LOG_MARK, Apache::LOG_ERR, 0, "log_rerror logging at err level"); $s->log_rerror(Apache::LOG_MARK, Apache::LOG_DEBUG, APR::ENOTIME, "debug print"); "$r->log()" my $rlog = $r->log; Similar to "$s->log()" the emerg(), alert(), crit(), error(), warn(), notice(), info(), debug() methods Similar to the server's log functions with the same names. For example: $rlog->debug("just ", "some debug info"); $rlog->warn(@req_warnings); $rlog->crit("dying"); General Functions "Apache::LOG_MARK()" my($file, $line) = Apache::LOG_MARK(); Though looking like a constant, this is a function, which returns a list of two items: "(__FILE__, __LINE__)", i.e. the file and the line where the function was called from. Aliases "$s->warn()" $s->warn(@warnings); is the same as: $s->log_error(Apache::LOG_MARK, Apache::LOG_WARNING, 0, @warnings) For example: $s->warn('routine server warning'); "Apache->warn()" "Apache::warn()" Apache->warn(@warnings); perl v5.8.0 2002-08-14 LOG(1)
All times are GMT -4. The time now is 06:32 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy