[Ltsp-developer] getltscfg for individual thin clients

[Frantisek Hanzlik]

Agree, I found it, see my previous post. This my bad assumption was
because LTSP 5 in Fedora is naming clients as "client-IP_ADDR" in
contrast with LTSP 4-, where client hostname was taken from resolver.
I had lts.conf from LTSP 4, where individual client entries was in
form "WSName.mysite.com". I then rewrite them to "client-$IPADDR",
but in process solving this problem I wrongly thought about getltscfg
behavior.
I know entries in lts.conf may be specified as MAC addresses,
IP addresses or FQDN names.

I'm not sure when above Fedora 9 client naming behavior is by
any way configurable, but IMHO setting client hostname from
resolver (if it is possible) is better then hard setting to
client-$IPADDR.

Franta Hanzlik

Gideon Romm wrote:
> getltscfg -a   does not only process the [default] section.  It
> processes the individual workstation configuration.  The '-a' simply
> means report all parameters (as opposed to just a single parameter).
>
> I hope this clears up the confusion.  You should never need anything
> but "getltscfg -a"
>
> -Gadi
>
> On Sun, May 18, 2008 at 9:37 PM, Warren Togami<wtogami at redhat.com>  wrote:
>> Frantisek Hanzlik wrote:
>>> Hello,
>>>
>>> in little connection with lp_server, I forgot one thing - F9 ltsp-1.5.7
>>> scripts nowhere calls 'getltscfg -n' for thin clients individual
>>> settings, thus only [default] section of lts.conf is processed - it
>>> is by calling 'getltscfg -a' at beginning of "ltsp_config" script
>>> (which is then included in several others scripts).
>>>
>>> My workaround about this was put "getltscfg -n" command at start
>>> of "ltsp-init-common" script:
>>>
>>> --- ltsp-init-common.OLD    2008-05-07 23:13:50.000000000 +0200
>>> +++ ltsp-init-common    2008-05-19 03:13:56.000000000 +0200
>>> @@ -7,6 +7,7 @@
>>>       msg="$1"
>>>       logger -p user.warning -t ltsp-client  "warning: $msg"
>>>   }
>>> +getltscfg -n        # get client specific settings
>>>
>>>   start_sound() {
>>>       if boolean_is_true "$SOUND" ; then
>>>
>> Grepping through ltsp-trunk I don't see Debian doing anything like this.
>>   How is Debian's LTSP using individual client settings?
>>
>> Warren Togami
>> wtogami at redhat.com
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Microsoft
>> Defy all challenges. Microsoft(R) Visual Studio 2008.
>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>> _____________________________________________________________________
>> Ltsp-developer mailing list.   To un-subscribe, or change prefs, goto:
>>       https://lists.sourceforge.net/lists/listinfo/ltsp-developer
>> For additional LTSP help,   try #ltsp channel on irc.freenode.net
>>
>
> _______________________________________________
> K12Linux-devel-list mailing list
> K12Linux-devel-list at redhat.com
> https://www.redhat.com/mailman/listinfo/k12linux-devel-list
>
> !DSPAM:4831979789059012215599!
>