I want to find the pid ( by ps ) that has already run over 30 seconds , I know ps only show the minute/hour .
eg. the start time of the below process are 15:19 / 15:20 , but I don't know the exact time ( in term of "second" ) it start to run ( I only know the hour and minute ) , if I want to... (2 Replies)
Except the command "top" , is there other function / tool is used to check the process status in the system like
1. what process are running ?
2. how the CPU are allocating ?
3. how many swap is using ?
4. "
Thx. (1 Reply)
Hi guys
I installed this new server with 5.0.7 openserver and i'm getting a lot of this process, if a stop and restart the printer spooler they go away but after a few minutes they appear again.This is how it looks like.
root 372 615 0 - - 00:00:00 <defunct>
root ... (0 Replies)
A coworker has a shell script that runs from a scheduler at the 3am. The shell script runs sqlplus passing in a sql statement, which generate a file. This is done 21 times for 21 different sql statements. Recently, one of the sqlplus processes got hung.
Is there a way to monitor how long the... (2 Replies)
Is there a way I can run a command that will run in the kernel or in the memory and automatically kill certain scripts if they get to <defunct> processes, without having to be monitoring the server manually?
I have a Perl script which runs for 20k members and normally does not have any problems,... (2 Replies)
Our network administrators implemented some sort of check to kill idle sessions and now burden is on us to run some sort of keep alive. Client based keep alive doesn't do a very good job. I have same issue with ssh. Does solution 2 provided above apply for ssh sessions also? (1 Reply)
Hi all
I have networker running on a RHEL 5.7 and over time it hangs. So the solution backup team proposed is to check if the process is hung, to stop and start it.
Unfortunately for me, the rc script only allows three commands, start, stop and status (no restart option) so I managed to set... (15 Replies)
I have process1 running on one machine and generating some log file. Now another process which can be launched on any machine wants to know if process1 is running or not and also in case it is running it wants to stream the logs file generated by process1 on terminal from which process2 is... (2 Replies)
I have a multithreaded usermode program(actually a daemon) which is in hanged state.
To debug it I tried attaching the process to gdb, but the gdb hangs.
gstack also gets hanged.
I peeped into the proc file system and saw the process to be in sleeping state.
/proc/sysrq-trigger I guess... (1 Reply)
Discussion started by: rupeshkp728
1 Replies
LEARN ABOUT CENTOS
doveadm-log
DOVEADM-LOG(1) Dovecot DOVEADM-LOG(1)NAME
doveadm-log - Locate, test or reopen Dovecot's log files
SYNOPSIS
doveadm [-Dv] log errors [-s min_timestamp]
doveadm [-Dv] log find [directory]
doveadm [-Dv] log reopen
doveadm [-Dv] log test
DESCRIPTION
The doveadm log commands are used to locate and reopen the log files of dovecot(1). It's also possible to test the configured targets of
the *log_path settings.
OPTIONS
Global doveadm(1) options:
-D Enables verbosity and debug messages.
-v Enables verbosity, including progress counter.
COMMANDS
log errors
doveadm log errors [-s min_timestamp]
The log errors command is used to show the last - up to 1,000 - errors and warnings. If no output is generated, no errors have occurred
since the last start.
-s min_timestamp
An integer value, representing seconds since the epoch - also known as Unix timestamp. When a min_timestamp was given, doveadm(1)
will only show errors occurred since that point in time.
log find
doveadm log find [directory]
The log find command is used to show the location of the log files, to which dovecot(1) sends its log messages. If dovecot(1) logs its
messages through syslogd(8) and doveadm(1) could not find any log files, you can specify the directory where your syslogd writes its log
files.
log reopen
doveadm log reopen
This command causes doveadm to reopen all log files, configured in the log_path, info_log_path and debug_log_path settings. These settings
are configured in /etc/dovecot/conf.d/10-logging.conf.
This is for example useful after manually rotating the log files.
log test
doveadm log test
This command causes doveadm to write the message "This is Dovecot's priority log (timestamp)" to the configured log files. The used prior-
ities are: debug, info, warning, error and fatal.
EXAMPLE
This example shows how to locate the log files used by dovecot(1).
doveadm log find
Looking for log files from /var/log
Debug: /var/log/dovecot.debug
Info: /var/log/mail.log
Warning: /var/log/mail.log
Error: /var/log/mail.log
Fatal: /var/log/mail.log
REPORTING BUGS
Report bugs, including doveconf -n output, to the Dovecot Mailing List <dovecot@dovecot.org>. Information about reporting bugs is avail-
able at: http://dovecot.org/bugreport.html
SEE ALSO doveadm(1)Dovecot v2.2 2013-11-24 DOVEADM-LOG(1)