On Wed, Mar 11, 2009 at 02:29:46PM -0400, Bob Doolittle wrote:
> Nick Ross wrote:
> > I'd try 'utsession -p -x', you'll find all the information there in an 
> > easy-to-parse format.  The only drawback is that it requires root 
> > privileges to run.
> >   
> 
> No, it has a much bigger drawback. It also does a utauthd callback, so 
> is expensive and impacts a critical system service, plus it does a lot 
> more work than is required for a single token lookup since it's 
> reporting status for all sessions. This is particularly significant in 
> Kiosk startup scripts, since when a FOG comes online (e.g. after a 
> network outage) a lot of DTUs may connect at once and attempt to run 
> Kiosk startup scripts simultaneously. utauthd can become a significant 
> bottleneck in this case if you rely on commands that do utauthd 
> callbacks in your scripts - utauthd's primary responsibility is 
> connecting DTUs to sessions. Generally speaking, any command that 
> reports "connected" status for DTUs is doing utauthd callbacks. This 
> includes utsession -p, utwho -c, utuser -c, and utdesktop -c.
> 
> utuser -p is the way to go here.

Glad that "utuser -p" is on the right lines at least :)

But there's no real lightweight way to get the DTU token ?  I need to be
able to disable speaker output if a session is migrated to a DTU in,
say, a library for example.

Thanks,

Ceri
-- 
That must be wonderful!  I don't understand it at all.
                                                  -- Moliere

Attachment: pgp9lPJxHAwXm.pgp
Description: PGP signature

_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users

Reply via email to