Sponsored Content
Top Forums Shell Programming and Scripting Utilities not dying after script run Post 302770806 by DGPickett on Monday 18th of February 2013 12:03:12 PM
Old 02-18-2013
You might want to capture your 'top' output once in a file or env var, so all the commands get data from the same moment.
This User Gave Thanks to DGPickett For This Post:
 

8 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

How to manage multiple versions of a set of shell and SQL script utilities

Hi all --- I have the need to manage multiple versions of a set of utility scripts -- both shell and SQL and other .dat files. I am wondering if anyone out there knows of a good way to "PATH" to SQL and text files in a way similar to how PATH facilitates finding executables in a pre-specified... (2 Replies)
Discussion started by: DennisB
2 Replies

2. Ubuntu

Internet dying in Debian?

For some reason after a while my internet connection dies. I just moved on to Debian from Ubuntu and I can't find the dhclient-program to reconfigure dhcp. Pretty new to *nix's. ONe thing I noticed while rebooting (do get my connection back) is that it configures dhcp and says: reconfigure (or... (1 Reply)
Discussion started by: riwa
1 Replies

3. UNIX for Dummies Questions & Answers

how to run utilities

I have utilities installed on a UNIX platform and was wondering how i run them. (1 Reply)
Discussion started by: hershey101
1 Replies

4. IP Networking

network connection dying after an uptime of a day or two days

hie guys I am running fedora 6 on remote machines which are connecting to my server. The remote machines connect through one machine (more like my router) to the server. The problem i am having is that the remote machines are suppose to be reporting in real time mode to the server. Most of these... (2 Replies)
Discussion started by: no3more
2 Replies

5. Programming

Java application dying randomly

Hi, (First post, please be gental!) I have a java app that I am running on unix (centos) But it keeps dying randomly. The times seem random from anything between 3 hours and 3 days. I have a cronjob running to restart it when ever it dies but I would rather this happened less often. ... (2 Replies)
Discussion started by: sm9ai
2 Replies

6. Shell Programming and Scripting

Expect script cronjob running but dying prematurely

I have an Ubuntu machine that I'd like to update automatically. I've written an expect script to run the aptitude package manager and update my packages. Essentially it does: aptitude update && aptitude upgrade while answering "yes" at the appropriate time. It works quite nicely when run... (4 Replies)
Discussion started by: CluelessPerson
4 Replies

7. Red Hat

Snmpd dying on centos7.1

Hello All, SNMPD dying after 2 mins once it started. Here is the configuration Oct 12 04:43:00 localhost systemd: Starting Simple Network Management Protocol (SNMP) Daemon.... Oct 12 04:43:00 localhost snmpd: dlopen failed: /usr/lib64/libcmaX64.so: cannot open shared object file: No such... (1 Reply)
Discussion started by: shekar777
1 Replies

8. What is on Your Mind?

Are the BSDs dying?

Source a quick google search making clear that this isn't really new, and if we look at our bsd Forum we see that its the only operation systems forum with the last comment dated to June last year, whereas all the others have more recent comments. One comment dated to 2014 is exactly what I... (10 Replies)
Discussion started by: dodona
10 Replies
ENV(1)							    BSD General Commands Manual 						    ENV(1)

NAME
env -- set and print environment SYNOPSIS
env [-i] [name=value ...] [utility [argument ...]] DESCRIPTION
env executes utility after modifying the environment as specified on the command line. The option name=value specifies an environmental variable, name, with a value of value. The option '-i' causes env to completely ignore the environment it inherits. If no utility is specified, env prints out the names and values of the variables in the environment, with one name=value pair per line. DIAGNOSTICS
If the utility is invoked, the exit status of env shall be the exit status of utility; otherwise, the env utility exits with one of the fol- lowing values: 0 The env utility completed successfully 1-125 An error occurred in the env utility. 126 The utility specified by utility was found, but could not be invoked. 127 The utility specified by utility could not be found. COMPATIBILITY
The historic - option has been deprecated but is still supported in this implementation. SEE ALSO
execvp(3), environ(7) STANDARDS
The env utility conforms to IEEE Std 1003.2-1992 (``POSIX.2''). BUGS
env doesn't handle commands with equal (``='') signs in their names, for obvious reasons. BSD
August 27, 1993 BSD
All times are GMT -4. The time now is 10:49 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy