home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!ogicse!hp-cv!sdd.hp.com!hplabs!ucbvax!UNODE2.NSWC.NAVY.MIL!SYSTEM_JM
- From: SYSTEM_JM@UNODE2.NSWC.NAVY.MIL ("SYSTEM SUPPORT")
- Newsgroups: comp.os.vms
- Subject: SHOW PROCESS SWAPPER
- Message-ID: <9208191543.AA08187@ucbvax.Berkeley.EDU>
- Date: 19 Aug 92 15:16:00 GMT
- Article-I.D.: ucbvax.9208191543.AA08187
- Sender: usenet@ucbvax.BERKELEY.EDU
- Organization: The Internet
- Lines: 28
-
-
- From: SYSTEM_JM@unode2.nswc.navy.mil
- >> Yikes! I'm sure there's an easy answer for this one! How come the
- >> command "$SHOW PROCESS <process-name>" works on our standalone system,
- >> but not on our cluster? For example: $ SHOW PROCESS SWAPPER will work
- >> on the standalone, but I get a "non-existent process" error on the
- >> cluster. And yes, the process does exist. Hmmm...
-
- From: Jerry Leichter <leichter@lrw.com>
- >Process names are implicitly qualified by group number: To see a process
- >selected by name, the group under which you are running has to match the
- >group under which the process is running. The SWAPPER runs under SYSTEM,
- >which is UIC [1,4]; so the "full" name of the process is [1]SWAPPER, where
- >the [n] part of the name can't be specified explicitly. I'll bet you are
- >running from a process in group 1, probably SYSTEM, on the standalone
- >system, but not on the cluster.
- > -- Jerry
-
- Well Jerry, if you were a bettin' man, you'd be rich! I was logged into
- the SYSTEM account on the standalone, but not on the cluster. Thanks a
- $billion for your response!
-
- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
- Jim Matthews
- Naval Surface Warfare Center Dahlgren Division
- Dahlgren, VA
- SYSTEM_JM%UNODE2@RELAY.NSWC.NAVY.MIL
- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-