On 12:42, venerd� 08 ottobre 2004, A.J. Venter wrote:
> Alternatively you can create a group called 'nodouble' and only suppress
> members of that group.
>
> It should be fairly simple to implement both options in ltspcfg and give
> the admin the option to then choose
> 1) allow all multi-logins
> 2) suppress all multi-logins except for group "multilogin"
> 3) suppress multi-logins only for group "nodouble"
>

agreed, but I like strong name space in groups, so I suggest names like: 
"ltsp_xdbl" (btw, one can think to refine the system creating "ltsp_shelldbl" 
and so on ..  in ltspcfg it should suffice to have an array @logins (x, 
shell, ..) to loop in, being able to handle every future access-method one 
will want.

It should be good to have an array of arrays, "types" and "descriptions",

pseudo-code:

logins=array(
   array('x', 'Allows double X sessions'),
   array('shell', 'Allows double shell login'),
)

foreach  logins as $log
{
print $log;
  1) allow all multi-logins
  2) suppress all multi-logins except for users in group "ltsp_{$log}dbl"
  3) allow multi-logins only for users in group "ltsp_{$log}dbl"
}


something similar :-)

btw, I think 1 group per $log should suffice, 2 are redundant

-- 
<?php echo '       Emiliano `AlberT` Gabrielli       ',"\n",
           '  E-Mail: AlberT_AT_SuperAlberT_it  ',"\n",
           '  Web:    http://SuperAlberT.it  ',"\n",
'  IRC:    #php,#AES azzurra.com ',"\n",'ICQ: 158591185'; ?>


-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_____________________________________________________________________
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net

Reply via email to