Sponsored Content
Top Forums Shell Programming and Scripting AIX subsystem stops partially Post 303044605 by MadeInGermany on Thursday 27th of February 2020 03:11:23 PM
Old 02-27-2020
In addition, ensure that kill is only run with arguments.
Code:
[ -z "$PID" ] || kill -9 $PID

 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

NFS client subsystem hang up on boot

Hi, I have a Unix box running HP-UX 10.20 and it suddenly won't boot. Every time it goes down the boot checklist, it hangs on "NFS client subsystem" and just continues to say busy/wait. I have read something about the /etc/auto_master but don't quite understand what has to happen to fix it. ... (4 Replies)
Discussion started by: Asheley Ryan
4 Replies

2. UNIX for Advanced & Expert Users

subsystem failure

aix 4.3 I get the following error from the errpt log BD797922 0306170008 P H enclosure0 SUBSYSTEM FAILURE I'm not clear on this kind of error. It never happened to me. What do this errors mean, and how do I clear or solve them? Any help is appreciated. (2 Replies)
Discussion started by: andwhat
2 Replies

3. AIX

Subsystem Component Failure

Hello All, Does some one have any idea about the subsystem component failure. Errpt command throws below errors for my server :- # errpt IDENTIFIER TIMESTAMP T C RESOURCE_NAME DESCRIPTION B9735AF4 0304222408 P H hdisk5 SUBSYSTEM COMPONENT FAILURE B9735AF4 0304222408 P H... (1 Reply)
Discussion started by: Shrek
1 Replies

4. AIX

Generating a Subsystem

Hello, I'm trying to generate a subsystem which supports startsrc, stopsrc and refresh I want to specify special arguments in case of stopsrc and refresh for example: startsrc: /bin/testscript start stopsrc: /bin/testscript stop refresh: /bin/testscript restart which should be... (0 Replies)
Discussion started by: funksen
0 Replies

5. AIX

AIX 5.3 ML10 new install, rsh only partially working

Two boxes we just reloaded to use as a two node HACMP cluster to insure our software is compatible. Install disks we received at our library on 5/2009 AIX 5.3-ML10 For sake of argument names ibmaix1 and ibmaix2 On both: ibmaix1# oslevel -r 5300-10 .rhosts files with 600 permissions... (0 Replies)
Discussion started by: DrKillPatient
0 Replies

6. Ubuntu

Getting Subsystem ID/Vendor

Hey Guys ... How I can look up Subsystem ID of the WIFI card under Ubuntu... I did try lspci but its outputting only Vendor and Dev no subsys ... I need same data as below ( Windows ) PCI\VEN_168C&DEV_001C&SUBSYS_04281468&REV_01\4&1BF192B7&0&0020 thank you happy new year ! (2 Replies)
Discussion started by: NDxiak
2 Replies

7. UNIX for Dummies Questions & Answers

SFTP subsystem requests

Hi there, what is the meaning of this line: SFTP subsystem requests: 5 Time(s) in: /var/mail/root??? Tks in advance, GB (0 Replies)
Discussion started by: Giordano Bruno
0 Replies

8. AIX

sftp : have to specify subsystem from client side

I have several ssh servers *running aix 5.3 and they respond to sftp requests just fine, but I have one that requires clients to specify the path to the sftp server using the -s flag which is*/usr/sbin/sftp-server I check the sshd_config across all servers and they are the same. *The other... (1 Reply)
Discussion started by: massdesign
1 Replies

9. HP-UX

[HP UNIX B.10.20] NFS Client SubSystem fail

Recently moved a HP Unix B.10.20 system from US to Thailand, and everything is work well in US but after we changed: 1. set_parms ip_address (change the IP to TH range) 2. set_parms addl_netwrk (change the Subnet, Gateway, Domain name, DNS Svr Name, and DNS IP) 3. vi /etc/hosts (to commented... (4 Replies)
Discussion started by: beta911
4 Replies

10. AIX

AIX 7.1 booting stops at C1922000 C19220FF

Hi, we have the p6 server running AIX 7.1 it suddenly stops working. I tried to re-cycle power but it keeps stopping at C19220FF. Activate the service processor pinhole reset switch but still stops at the same code. Error logs: 1. 501A1181 2016-06-08 22:06:20 'Service Process'... (1 Reply)
Discussion started by: lilyn
1 Replies
KILLALL(1)							   User Commands							KILLALL(1)

NAME
killall - kill processes by name SYNOPSIS
killall [-Z, --context pattern] [-e, --exact] [-g, --process-group] [-i, --interactive] [-n, --ns PID] [-o, --older-than TIME] [-q, --quiet] [-r, --regexp] [-s, --signal SIGNAL, -SIGNAL] [-u, --user user] [-v, --verbose] [-w, --wait] [-y, --younger-than TIME] [-I, --ignore-case] [-V, --version] [--] name ... killall -l killall -V, --version DESCRIPTION
killall sends a signal to all processes running any of the specified commands. If no signal name is specified, SIGTERM is sent. Signals can be specified either by name (e.g. -HUP or -SIGHUP) or by number (e.g. -1) or by option -s. If the command name is not regular expression (option -r) and contains a slash (/), processes executing that particular file will be selected for killing, independent of their name. killall returns a zero return code if at least one process has been killed for each listed command, or no commands were listed and at least one process matched the -u and -Z search criteria. killall returns non-zero otherwise. A killall process never kills itself (but may kill other killall processes). OPTIONS
-e, --exact Require an exact match for very long names. If a command name is longer than 15 characters, the full name may be unavailable (i.e. it is swapped out). In this case, killall will kill everything that matches within the first 15 characters. With -e, such entries are skipped. killall prints a message for each skipped entry if -v is specified in addition to -e, -I, --ignore-case Do case insensitive process name match. -g, --process-group Kill the process group to which the process belongs. The kill signal is only sent once per group, even if multiple processes belonging to the same process group were found. -i, --interactive Interactively ask for confirmation before killing. -l, --list List all known signal names. -n, --ns Match against the PID namespace of the given PID. Use 0 to match against all namespaces. The default is to match against the current PID namespace. -o, --older-than Match only processes that are older (started before) the time specified. The time is specified as a float then a unit. The units are s,m,h,d,w,M,y for seconds, minutes, hours, days, weeks, Months and years respectively. -q, --quiet Do not complain if no processes were killed. -r, --regexp Interpret process name pattern as a POSIX extended regular expression, per regex(3). -s, --signal, -SIGNAL Send this signal instead of SIGTERM. -u, --user Kill only processes the specified user owns. Command names are optional. -v, --verbose Report if the signal was successfully sent. -V, --version Display version information. -w, --wait Wait for all killed processes to die. killall checks once per second if any of the killed processes still exist and only returns if none are left. Note that killall may wait forever if the signal was ignored, had no effect, or if the process stays in zombie state. -y, --younger-than Match only processes that are younger (started after) the time specified. The time is specified as a float then a unit. The units are s,m,h,d,w,M,y for seconds, minutes, hours, days, weeks, Months and years respectively. -Z, --context (SELinux Only) Specify security context: kill only processes having security context that match with given extended regular expres- sion pattern. Must precede other arguments on the command line. Command names are optional. FILES
/proc location of the proc file system KNOWN BUGS
Killing by file only works for executables that are kept open during execution, i.e. impure executables can't be killed this way. Be warned that typing killall name may not have the desired effect on non-Linux systems, especially when done by a privileged user. killall -w doesn't detect if a process disappears and is replaced by a new process with the same PID between scans. If processes change their name, killall may not be able to match them correctly. killall has a limit of names that can be specified on the command line. This figure is the size of an unsigned long multiplied by 8. For most 32 bit systems the limit is 32 and similarly for a 64 bit system the limit is usually 64. SEE ALSO
kill(1), fuser(1), pgrep(1), pidof(1), pkill(1), ps(1), kill(2), regex(3). psmisc 2017-06-12 KILLALL(1)
All times are GMT -4. The time now is 04:17 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy