Man page - pmsignal(1)
Packages contains this manual
- pmie(1)
- pmie2col(1)
- pcp-netstat(1)
- pmdanetcheck(1)
- pmdammv(1)
- dbpmda(1)
- pcp2openmetrics(1)
- pmlogdump(1)
- pcp-dmcache(1)
- pmdabonding(1)
- webpingvis(1)
- pmdaxfs(1)
- nfsvis(1)
- pmclient(1)
- pcp-ipcs(1)
- pcp-buddyinfo(1)
- pmdanvidia(1)
- pmdasimple(1)
- pmdanfsclient(1)
- pmdalibvirt(1)
- pcp-atoprc(5)
- osvis(1)
- pmdaamdgpu(1)
- pmdbg(1)
- pmdabind2(1)
- pcp.env(5)
- pmlogsummary(1)
- pmrepconf(1)
- pmstat(1)
- pcp-pidstat(1)
- pcp-collectl(1)
- pmdagpfs(1)
- pmstore(1)
- pmdalio(1)
- pmerr(1)
- pmdamailq(1)
- pmdahaproxy(1)
- pcp-python(1)
- pmlogger.control(5)
- mkaf(1)
- pcp2csv(1)
- pmdabcc(1)
- pmie_daily(1)
- pmlogredact(1)
- pmiostat(1)
- pmdaopenvswitch(1)
- pmsleep(1)
- pcp-iostat(1)
- pmdatrace(1)
- pmdafarm(1)
- pmdakvm(1)
- pcp-htop(5)
- perfevent.conf(5)
- pmnsdel(1)
- pmafm(1)
- pmdagpsd(1)
- pmdaweblog(1)
- pmdasamba(1)
- pmdamic(1)
- chkhelp(1)
- pmsearch(1)
- pmlogconf(1)
- pmdapostgresql(1)
- pmloglabel(1)
- pmlogsize(1)
- genload(1)
- pcp-numastat(1)
- pmlogcheck(1)
- pmiestatus(1)
- pcp-slabinfo(1)
- pmcd_wait(1)
- runaspcp(1)
- pcp-atop(1)
- indomcachectl(1)
- pmdagluster(1)
- pcp-free(1)
- dstat(1)
- pcp-mpstat(1)
- pmdatxmon(1)
- pmwebd(1)
- pcp-uptime(1)
- dbprobe(1)
- pmdaunbound(1)
- pmdasockets(1)
- pmdadenki(1)
- pmdanetbsd(1)
- pmlogmv(1)
- mpvis(1)
- pmdasolaris(1)
- pmfind(1)
- pmdawindows(1)
- pmlogextract(1)
- pmval(1)
- pmclient_fg(1)
- pmdads389(1)
- pcp-htop(1)
- pmlogbasename(1)
- pminfo(1)
- pmlogger_daily_report(1)
- pcp-lvmcache(1)
- pmdadbping(1)
- pmlogpaste(1)
- pmview(5)
- pmdaroot(1)
- pmdahacluster(1)
- pmdaperfevent(1)
- pmdate(1)
- pmdasendmail(1)
- pmcpp(1)
- pmdaoracle(1)
- pmdajson(1)
- txrecord(1)
- pcp-shping(1)
- pcp-ps(1)
- pmdadocker(1)
- pmdanews(1)
- pmevent(1)
- pmdamounts(1)
- pmdamysql(1)
- pmlogcompress(1)
- pmdabpftrace(1)
- pcp-check(1)
- pcp-verify(1)
- pmpause(1)
- pmfind_check(1)
- pmdaactivemq(1)
- pmlock(1)
- pmprobe(1)
- pmdanamed(1)
- pmnsmerge(1)
- dkvis(1)
- genpmda(1)
- pmview(1)
- pmdalustre(1)
- pmlogger(1)
- pmdaroomtemp(1)
- pcp-ss(1)
- labels.conf(5)
- pmdasummary(1)
- pmdasample(1)
- pmrep(1)
- pmdanetfilter(1)
- pcp-geolocate(1)
- pmdalogger(1)
- pmlogger_daily(1)
- pmtrace(1)
- pmdapipe(1)
- pmlogrewrite(1)
- pmdiff(1)
- pmdauwsgi(1)
- pcp.conf(5)
- pmpost(1)
- pmdajbd2(1)
- pmdarabbitmq(1)
- pmdapodman(1)
- pmdaapache(1)
- pmdabash(1)
- pmdumplog(1)
- pmdasmart(1)
- pmdagfs2(1)
- pmdadarwin(1)
- pmdaelasticsearch(1)
- pmpython(1)
- newhelp(1)
- pmdabpf(1)
- pmdaslurm(1)
- pmlogreduce(1)
- pcp-atopsar(1)
- pmnsadd(1)
- pcp-dstat(5)
- pmdazimbra(1)
- pmdasnmp(1)
- pcp-tapestat(1)
- pmdadm(1)
- pmieconf(5)
- pmdafreebsd(1)
- pmdatrivial(1)
- pmgetopt(1)
- pmconfig(1)
- pmdalinux(1)
- pmlogger_merge(1)
- weblogvis(1)
- pmdaresctrl(1)
- pmdashping(1)
- pmgenmap(1)
- pmdamssql(1)
- perfalloc(1)
- pmdanginx(1)
- pmdazfs(1)
- pmproxy(1)
- pcp-kube-pods(1)
- pmdazswap(1)
- pmdamemcache(1)
- pmrep.conf(5)
- pmdaproc(1)
- pmcd(1)
- pmdaoverhead(1)
- pmdaredis(1)
- pcp-meminfo(1)
- pmie_dump_stats(1)
- pmdaopenmetrics(1)
- pmdacisco(1)
- pmdaaix(1)
- pcp-summary(1)
- pmdalmsensors(1)
- pmlogger_rewrite(1)
- clustervis(1)
- pcp-reboot-init(1)
- pcp-dstat(1)
- pmdalustrecomm(1)
- pmhostname(1)
- pcp-zoneinfo(1)
- pcp(1)
- pmdarsyslog(1)
- pcp-vmstat(1)
- pmdacifs(1)
- pmieconf(1)
- pmmgr(1)
- pmie_check(1)
- pmjson(1)
- pmseries(1)
- pmdapostfix(1)
- pmdamongodb(1)
- telnet-probe(1)
- pmsocks(1)
- pmlogger_check(1)
- pmlc(1)
- pmlogctl(1)
- pmdapdns(1)
- pmdads389log(1)
- pmiectl(1)
- pcp-xsos(1)
- pmdanutcracker(1)
- webvis(1)
- find-filter(1)
- pmsignal(1)
apt-get install pcp
Manual
PMSIGNAL
NAMESYNOPSIS
DESCRIPTION
OPTIONS
PCP ENVIRONMENT
SEE ALSO
NAME
pmsignal - send a signal to one or more processes
SYNOPSIS
$PCP_BINADM_DIR/pmsignal [ -alnp ] [ -s signal ] [ PID ...| name ...]
DESCRIPTION
pmsignal provides a cross-platform event signalling mechanism for use with tools from the Performance Co-Pilot toolkit. It can be used to send a named signal (only HUP, USR1, TERM, and KILL are accepted) to one or more processes.
The processes are specified directly using PIDs or as program names (with either the -a or -p options). In the all case, the set of all running processes is searched for a basename (1) match on name . In the program case, process identifiers are extracted from files in the $PCP_RUN_DIR directory where file names are matched on name .pid.
The -n option reports the list of process identifiers that would have been signalled, but no signals are actually sent.
If a signal is not specified, then the TERM signal will be sent. The list of supported signals is reported when using the -l option.
On Linux and UNIX platforms, pmsignal is a simple wrapper around the kill (1) command. On Windows, the is no direct equivalent to this mechanism, and so an alternate mechanism has been implemented - this is only honoured by PCP tools, however, not all Windows utilities.
OPTIONS
The available
command line options are:
-a
,
--all
Send signal to all named processes.
-l , --list
List supported signals.
-n , --dry-run
List processes that would be affected.
-p , --program
Extract programs from PCP runtime PID files.
-s signal , --signal = signal
Specify the signal to send, one of: HUP, USR1, TERM, KILL.
-? , --help
Display usage message and exit.
PCP ENVIRONMENT
Environment variables with the prefix PCP_ are used to parameterize the file and directory names used by PCP. On each installation, the file /etc/pcp.conf contains the local values for these variables. The $PCP_CONF variable may be used to specify an alternative configuration file, as described in pcp.conf (5).
SEE ALSO
basename (1), kill (1), killall (1), pcp.conf (5) and pcp.env (5).