"{Darkavich} Steven Misrack" <[EMAIL PROTECTED]> wrote:
> 1) utnetpipe not found on SRSS2 systems
Right, it was new in 3.0. If you copy the 3.0 executable to
your 2.0 machine it should be fine, although I haven't tried
it. Or use netcat ('nc') if that's installed on your 2.0
system. Several SRSS scripts used to use the /dev/tcp
built-in in 'ksh' for this kind of thing but that was ugly.
Luckily the Linux 'pdksh' doesn't support that built-in so
we took the opportunity to switch to something more
straightforward in 3.0.
> 2) on a multi-head (no xinerama)
> main sunray returned null
> secondary sunray returned the primary mac.
>
>On primary
>sr-test-san:smisrack [387]echo "status tokenName=$SUN_SUNRAY_TOKEN"
>status tokenName=user.1121181178-7053
>
>On secondary
>sr-test-san:smisrack [90]echo "status tokenName=$SUN_SUNRAY_TOKEN"
>status tokenName=auth.smisrack
That's bizarre. How did you end up with two different values of
$SUN_SUNRAY_TOKEN in one desktop login?
That script will always report the client ID of the primary DTU
in a multihead session, which is why it reported
IEEE802.0003ba4ea62b when you ran it on the secondary head.
Programs generally have no idea which DTU of a multihead group
their output is going to. It'd take a far more complex program
than a 17-line shell script to figure that out.
It should have reported IEEE802.0003ba4ea62b when you ran it on
the primary too, but it was misled by the strange token value
in that shell's environment.
OttoM.
__
ottomeister
--
___________________________________________________________
Sign-up for Ads Free at Mail.com
http://promo.mail.com/adsfreejump.htm
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
