Re: getltscfg for individual thin clients
Warren Togami <[email protected]>
| Newsgroups | gmane.linux.terminal-server.devel |
|---|---|
| Message-ID | <[email protected]> |
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
[email protected]
-------------------------------------------------------------------------
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