PCP - maps ports to PIDs

6 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Get all associated pids

im looking for a portable way to get the PID of the script that is running, and to get every other PIDs that are spawned from it. and by ever other PIDs, i presume, that would be "child processes". however, i want to shy away from using any command that is not available on every single unix...

2. Shell Programming and Scripting

Need help to kill pids

Hi there !!! I am writing a script to kill the pids on different linux boxes :cool: the output of my command gives the pids running on that box, but how can I kill all the pids without looping? :confused: Code: ssh $i ps -fu $USER | grep ManServer | grep -v grep | awk '{print $2}' | kill ...

3. UNIX for Dummies Questions & Answers

/proc/pid/maps

I think the libc.so is shared between processes, because it is a shared library and OS is engaged for saving memory. But, below, the maps of bash, shows r-xp and r--p rw-p attributes to libc.so which mean private memory space. Can anybody explain this for me? :)cat /proc/$$/maps...

4. Solaris

Conflict with PIDs

I am trying to determine the root cause of a java process that dies trying to startup during it's cron job. I did go ahead and change the time that it starts up in the cron file and now it starts successfully. However is there a way to determine what PID a process was attempting to get when...

5. Red Hat

read maps from /proc/pid/

hi, i hav a query abt reading the contents of /proc/pid/maps file.is there any system apis or functions available to get the data from dat file and parse according to my need. i need name of the .so,Create date of the .so file.,Location of .so file etc. please provide a good source. yes i hav...

6. UNIX for Advanced & Expert Users

NIS Maps

Hello.. I stink at NIS! :) Im having a problem with NIS on solaris 2.X. / SPARC I have some maps that are exported to all clients in the domain. Now I setup a new server and add it as a nis client to the domain. On the NIS server there is a auto_direct map that mounts /usr/local . This is...

LEARN ABOUT DEBIAN

aconnect

aconnect(1)						      General Commands Manual						       aconnect(1)

NAME

       aconnect - ALSA sequencer connection manager

SYNOPSIS

       aconnect [-d] [-options] sender receiver
       aconnect -i|-o [-options]
       aconnect -x

DESCRIPTION

       aconnect  is  a	utility  to connect and disconnect two existing ports on ALSA sequencer system.  The ports with the arbitrary subscription
       permission, such as created by aseqview(1), can be connected to any (MIDI) device ports using aconnect.	For example, to connect from  port
       64:0 to 65:0, run as follows:

	   % aconnect 64:0 65:0

       The connection is one-way, and the whole data to the sender port (64:0) is redirected to the receiver port (65:0).  When another port (e.g.
       65:1) is attached to the same sender port, the data is sent to both receiver ports.  For disconnection, use -d option.

       % aconnect -d 64:0 65:0

       The address can be given using the client's name.

       % aconnect External:0 Emu8000:1

       Then the port 0 of the client matching with the string "External" is connected to the port 1 of the client matching with the "Emu8000".

       Another function of aconnect is to list the present ports on the given condition.  The input ports, which may become sender ports,  can	be
       listed with -i option.

       % aconnect -i
       client 0: 'System' [type=kernel]
	   0 'Timer	      '
	   1 'Announce	      '
       client 64: 'External MIDI-0' [type=kernel]
	   0 'MIDI 0-0	      '

       Similarly, to see the output ports, use -o flag.

       You  can  remove  all existing exported connections using -x option.  This function is useful for terminating the ALSA drivers, because the
       modules with sequencer connections cannot be unloaded unless their connections are removed.

OPTIONS

   CONNECTION MANAGEMENT
       -d, --disconnect
	      Disconnect the given subscription.

       -e, --exclusive
	      Connect ports with exclusive mode.  Both sender and receiver ports can be no longer connected by any other ports.

       -r, --real queue
	      Convert time-stamps of event packets to the current value of the given real-time queue.  This is option is, however, not so  useful,
	      since the receiver port must use (not necessarily own) the specified queue.

       -t, --tick queue
	      Like -r option, but time-stamps are converted to the current value of the given tick queue.

   LIST PORTS
       -i, --input
	      List existing input (readable) ports.  This option is exclusive to -o.

       -o, --output
	      List existing output (writable) ports.  This option is exclusive to -i.

       -l, --list
	      List the current connection status.  The connected and connecting ports from/to each port are listed together.  The suffix flag [ex]
	      means the connection is exclusive.  The suffix flag [real:#] and [tick:#] mean the connection includes real-time and tick conversion
	      on the listed queue, respectively.

   REMOVE ALL CONNECTIONS
       -x, --removeall
	      Remove all exported connections.

SEE ALSO

       aseqnet(1), aseqview(1)

AUTHOR

       Takashi Iwai <tiwai@suse.de>

								  August 31, 2000						       aconnect(1)

Solaris BigAdmin RSS