Sponsored Content
Operating Systems Solaris Need Information About Process Post 302297752 by incredible on Sunday 15th of March 2009 04:00:12 AM
Old 03-15-2009
incorporate a timestamp within the script to capture the starttime and endtime and pipe the information to a text file. from there you will know. you need not check the process at all for this.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Process Information

Hi, If we have a process p1 running and then p2 attempts to shutdown p1. Is there a means for p1 to know who has requested him to shutdown Thanks and regards, Reji (1 Reply)
Discussion started by: rejise
1 Replies

2. Programming

Process Run time information

Hello, I am working on Sun Solaris 5.7. I am trying to read the running time of a process through a C program. One way I am reading it is by using the command ps -<pid> -f The other way is from the struct psinfo_t which is there under /proc/pid/psinfo. However, the two times are... (1 Reply)
Discussion started by: hmurali
1 Replies

3. Programming

Obtaining Process information on AIX

I have written a program to collect some performance metrics on and AIX box, but I'm having difficultly getting the process information. I'm lead to believe that I'm not getting the correct information because I'm trying to run the program on AIX 5.1 (5100-03), but I'm not convinced as the... (0 Replies)
Discussion started by: StuBob
0 Replies

4. Shell Programming and Scripting

Report Process Information (Help me)

I need a script to record top 5 processes to a file. I need the timestamp, cpu and memory utilization along with the process ID. Thanks in advance! (1 Reply)
Discussion started by: jabcd
1 Replies

5. Shell Programming and Scripting

get process information remotely

Hello, We have a domain where instances attached to it are in multiple machines. Is there any way that I can get the process information of the domain of a secondary server from the primary. ssh authentication is enabled on the functional ID and if I scsu to that ID and do the ssh: $ssh machine2... (0 Replies)
Discussion started by: chiru_h
0 Replies

6. UNIX for Dummies Questions & Answers

Process information

What sort of statistical information related to a running process can we retrieve using commands? For example, we can get the process id, memory usage and running time of a process using the commands ps and ipcs . Can we get any more information about a running process? Please list them. Also... (4 Replies)
Discussion started by: fermisoft
4 Replies

7. Shell Programming and Scripting

get Thread information from process

Hello all im trying to build small script in tcsh that will monitor some process that are making some api calles to some server . first of all im trying to find way to see how many threads each process is using , and else how can i print each Thread id . can it be done ? ( using sunOs ) (2 Replies)
Discussion started by: umen
2 Replies

8. Programming

reading process information

Can any one tell me is there any problem in reading the /proc/#/status file for finding out the exact process name..??? (4 Replies)
Discussion started by: clintoo
4 Replies

9. Solaris

ZFS get process I/O information

Hi Guys Is it possible to display which process generates the most i/o on my zpool? With # zpool iostst 3 and iostat i just see the general i/o but not the i/o on the process level. thx in advance, Fry (0 Replies)
Discussion started by: fryzh
0 Replies

10. Shell Programming and Scripting

Process Scheduling Information Extraction

I want to extract the process having highest utilization on each processor core and then output its information (PID etc.) to a file. How can I do it by using either top or ps command? Thanks. (1 Reply)
Discussion started by: Vaibhavs1985
1 Replies
rdeliver(1)						      General Commands Manual						       rdeliver(1)

NAME
rdeliver - Ruby mail filter script SYNOPSYS
rdeliver <options> [script] DESCRIPTION
This script serves as an example of how you can use the RFilter::DeliveryAgent class to perform mail delivery. You can also use this script as a fully functioning mail filter. This script is a basic mail local delivery agent (DeliveryAgent) that can be used in place of procmail, maildrop, etc. in a user's .forward or .qmail file. The user supplies a delivery script that is written in Ruby, which avoids the limitations of the crippled mini-languages so often used in other DeliveryAgent programs. USAGE
rdeliver is invoked from the command line using: % rdeliver <options> [script] The script argument is optional. If omitted the script will look for a file called .rdeliver in the home directory. Options are: --load-path directory Prepend the given directory to ruby's load path. --log filename Log to the given filename. If no log is specified, no logging occurs. --home directory Specify the home directory. rdeliver will change to this directory before reading and writing any files. The home directory defaults to the value of the HOME or LOGDIR environment variable. DELIVERY SCRIPT
The delivery script runs in the context of a class called Deliver (in contrast, most ruby scripts run in the context of the Object class). So any methods added with def will be added to the Deliver class. A minimal delivery script would be: def main agent.save('inbox') end This code defines a Deliver#main method that saves the mail into an mbox style mailbox. The only API the Deliver script has is the #agent method. This retrieves the RFilter::DeliveryAgent object associated with the current message. Using the API of the RFilter::DeliveryAgent object, you can access and modify the message body and headers, defer or reject the message delivery, and deliver into various mailbox formats. See also RFilter::DeliveryAgent and Deliver. INSTALLATION
Assuming you have the RubyMail mail classes installed, you typically have to put something like this in your .forward file: |"/usr/bin/rdeliver --log /home/you/.rlog" This will call rdeliver for each new message you get, and log to /home/you/.rlog. CATASTROPHIC ERRORS
The rdeliver script is very careful with errors. If there is any problem, it logs the error to the log file you specify. But if you do not specify a log file, or the error occurs before the log file is opened, a record of the error is placed in a file called CATASTROPH- IC_DELIVERY_FAILURE in the home directory. If that fails, the error information is printed to the standard output in the hopes that it will be part of a bounce message. In all cases, the exit code 75 is returned, which tells the MTA to re-try the delivery again. AUTHOR
rdeliver and RFilter support classes were written by Matt Armstrong <matt@lickey.com>. This document was originally an RD format document of rdeliver script. This manual page was converted from it for Debian GNU/Linux system. September 2003 rdeliver(1)
All times are GMT -4. The time now is 06:04 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy