Phantoms can be differentiated from other processes by using @USER.TYPE=1
(UniData) or @TTY=phantom (UniVerse), there was an issue some time ago
(RedBack and UniVerse on UNIX specific) which may have given an unexpected
result for a while (long fixed).
If you want to check whether a non-PHANTOM
Kevin;
I believe the job schedule commands all start with MM. We check if
@command[1,2] = MM in our login routine.
hth
Colin Alfke
Calgary Canada
-Original Message-
From: Kevin King
I was under the impression that Redback sessions were always started
with @USER.TYPE = 0. However, a
From: [EMAIL PROTECTED]
I believe the job schedule commands all start with
MM. We check if @command[1,2] = MM in our login routine.
And then do what, specifically?
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
Sorry, we don't use Redback so I was hoping this would at least give you
an idea. We are simply trying to make sure that we separate the SB JSD
jobs (which need to go through SB.LOGIN) and our phantom jobs (which we
didn't want to go through SB.LOGIN).
I don't think SB.LOGIN logs off when done.
On 6/18/07, Kevin King [EMAIL PROTECTED] wrote:
I really need to be able to differentiate between SB+ and RB phantoms,
and right now I'm not seeing how to make it happen. Any ideas? Do RB
phantoms always start with the same @LOGNAME, perhaps?
Any RB connection is served up by the rgwsched
From: Andy Pflueger
Any RB connection is served up by the rgwsched responder
and by that Unix user that started/owns those responders.
That's somewhat helpful, but what is this WW.SB.RB thing that's in the
LOGIN? And is it normal that it will not start SB+ for job schedule
definitions?
---
