05-22-2019
Of course your usage text is better.
The original script is named "check_user_threads.sh" and that's what it did from the beginning. The procs measurement was added later, in a hurry, as Solaris servers with a proc limit (in /etc/system) showed up.
The usage message is sent to stdout on purpose, because stdout *must* go to the Nagios console. Not so with stderr. But maybe it works meanwhile.?
This User Gave Thanks to MadeInGermany For This Post:
10 More Discussions You Might Find Interesting
1. Solaris
Hi ,
I need to count all processes contains the pattren "FND"
For Example:
I was reteriving the details of all processes related to "FND" by this command
$ ps -ef | grep FND
but now I just wanna count them .
Regards
Adel (2 Replies)
Discussion started by: ArabOracle.com
2 Replies
2. UNIX for Dummies Questions & Answers
I have written a function that fills an array and another function where if a parameter is supplied it will jump to that part of the array and cat it to the screen.
I need to put in some checks to make sure the parameter supplied is firstly a number and then not a number great than the length of... (2 Replies)
Discussion started by: magnia
2 Replies
3. Programming
I need a mechanism to fork child processes and all child processes should connect to a server.but the number of child processes should be limited(for ex:50)
Here's my pseudo, but I cant figure out how to limit the child process number. Should I use a semaphore? or what?
for(;;)... (3 Replies)
Discussion started by: xyzt
3 Replies
4. Shell Programming and Scripting
Hi all
Is there away to create a script with dynamic number of parameter..
like the kill command in UNIX
kill -9 xxx xxx
cheers (4 Replies)
Discussion started by: co0oly
4 Replies
5. Shell Programming and Scripting
Hi
Is there a way to count how many processes a script has started, count how many of these have finished, and make the script wait if their difference goes over a given threshold?
I am using a script to repeatedly execute a code (~100x) which converts 2 data files into one .plt which is in... (4 Replies)
Discussion started by: drbones
4 Replies
6. Shell Programming and Scripting
Hey I'm new in linux,
I'm looking for a code to check whether the parameter is a number or a string.
I have already tried this code:
eerste=$(echo $1 | grep "^*$">aux)
if
But it doesn't work.:confused:
Thanks (2 Replies)
Discussion started by: Eclecticaa
2 Replies
7. AIX
Hi,
Is there a maximum number of processes kernel parameter in AIX.
Solaris has max_nprocs,
HP-UX has nproc,
I can only find max user process (maxuproc) for AIX.
Thanks,
Wilson. (3 Replies)
Discussion started by: wilsonee
3 Replies
8. AIX
Morning,
Somebody can tell me in AIX 6.1 what is the different between the maxuproc (lsattr -El sys0 | grep max) and the for a user.
Example:
Oracle is limited by :
#ulimit -u
processes(per user) unlimited
But lsattr -El sys0| grep maxuproc show me :
maxuproc 16384
So... (1 Reply)
Discussion started by: bacup540
1 Replies
9. UNIX for Dummies Questions & Answers
// AIX 6.1 & Power 7 server
I have maxuproc set to 16384.
lsattr -El sys0 -a maxuproc
maxuproc 16384 Maximum number of PROCESSES allowed per user True
What is the maximum number of maxuproc we can go for?
If I increase maxuproc to the higher number, what would be ramifications?
I... (1 Reply)
Discussion started by: Daniel Gate
1 Replies
10. Red Hat
Hi Guys,
I am running RHEL6 and now my processes reach maximum limit.
How do I increase the maxuproc value?
Can I increase the value without rebooting the server?
Thanks in advance...
Please Help!!! (5 Replies)
Discussion started by: Phuti
5 Replies
LEARN ABOUT SUSE
cups-driverd
cups-driverd(8) Apple Inc. cups-driverd(8)
NAME
cups-driverd - cups driver daemon
SYNOPSIS
cups-driverd cat ppd-name
cups-driverd list request_id limit options
DESCRIPTION
cups-driverd shows or lists PPD files. It is run in response to CUPS-Add-Modify-Printer or CUPS-Get-Devices requests. The first form
("cups-driverd cat ppd-name") writes the named PPD file to stdout. The output format is an uncompressed PPD file.
The second form lists the available manufacturers or PPD files to stdout as indicated by the options argument. The output format is an IPP
response message. The request_id argument is the request ID from the original IPP request, typically 1. The limit argument is the limit
value from the original IPP request - 0 means no limit. Finally, the options argument is a space-delimited list of attributes ("name=value
name=value ...") that were passed in with the request. Currently cups-driverd looks for the ppd-make and requested-attributes attributes
and tailors the output accordingly.
DRIVERS
Drivers can be static PPD files under the /usr/share/cups/model directory or programs under the /usr/lib/cups/driver directory. Static PPD
files must conform to the Adobe PPD File Format Specification version 4.3 and may be compressed using the gzip(1) program. Driver programs
must implement the command-line interface shown in the next section.
DRIVER PROGRAMS
Driver programs provide an interface to dynamically-generated PPD files. The following arguments are currently defined:
drivername list
Lists the supported PPD files to stdout.
drivername cat ppdname
Writes the named PPD file to stdout.
LISTING FILES (drivername list)
When run with the single argument "list", the program must list the available PPD files it can generate to stdout using the following for-
mat:
"drivername:ppdname" language "make" "make and model" "1284 device id"
Drivername is the name of the driver program. Ppdname is the name used to select the given driver. Language is the locale associated with
the default language of the PPD file, typically "en". Make is the Manufacturer name from the PPD file. Make and model is the NickName name
from the PPD file. 1284 device id is the 1284DeviceId from the PPD file, if any.
WRITING FILES (drivername cat ppdname)
When the driver program is run with the "cat ppdname" arguments, it must write the named PPD file to stdout, uncompressed. If the named PPD
file does not exist, the driver program must not write any output to stdout and report the error to stderr instead.
DRIVER ERROR MESSAGES
Error messages can be relayed back to cupsd by writing them to stderr. The following prefixes are recognized:
DEBUG: [drivername]
Debugging messages
ERROR: [drivername]
Error messages
INFO: [drivername]
Informational messages
SEE ALSO
cupsd(8), cupsd.conf(5), cupstestppd(1),
http://localhost:631/help
COPYRIGHT
Copyright 2007-2009 by Apple Inc.
16 June 2008 CUPS cups-driverd(8)