On Tue, Jul 8, 2008 at 9:10 PM, UTbloke <[EMAIL PROTECTED]> wrote: > On Wed, Jul 9, 2008 at 10:52 AM, ottomeister <[EMAIL PROTECTED]> wrote: >> If the DTU isn't connected to some other host in this server's group >> then it's a bug in 'utdesktop'. > > This is a standalone server in a test environment with a couple of DTU > where no DTU sessions exist (disconnected or otherwise) and no DTU > actually powered on.
Then I'd call it a bug. There is a window of few minutes where you can power off a DTU withut SRSS realising that the DTU has disappeared (it takes a while for the DTU's heartbeat connection to time out if the DTU goes dead) but it doesn't sound like that's what's happening here. > The only reason I found this is because I wanted to explore methods of > enumerating token readers that are 'Connected' without having to parse > through a (potentially) long list of DTU ...something along the lines > of using 'utreader' to list the readers and then maybe (?) using > 'utdesktop' to figure out which readers are actually available. > > While on the subject of command line output ...I'd love to see the > "utuser -r <reader" become a wee bit more script friendly ...like not > having to send a <CR> to read the token would be an improvement IMHO > ...comments? That sounds like a decent RFE. The 'utreader -r' concept is that it's an interactive command, but I could see adding an option to make it try to grab exactly one token value immediately and either succeed or fail without further interaction. OttoM. __ ottomeister Disclaimer: These are my opinions. I do not seak for my employer. _______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users
