No reaction following lts.conf changes

Discussion:

Radek Bursztynowski

2013-07-01 21:51:35 UTC

Hi,

I try to mange LTSP (5.9) with no effect.
Thin client starts, and I can logg in.

I arrange some changes in lts.conf and there is no effect.
I added in default section few lines as follow:

LC_ALL = pl_PL.UTF-8
LANG = pl_PL.UTF-8
XKBLAYOUT = pl
KEYTABLE = pl
LDM_LANGUAGE = pl_PL.UTF_8
X_COLOR_DEPTH = 24
HOTPLUG = True
LOCALDEV = Trye
SOUND = True
LOCAL_STORAGE = True
XINITRC_DAEMON = True
SYSLOG_HOST = server
TIMESERVER = 192.168.67.1

and I added section destined to my thin client:

[00:0E:0C:B5:88:CA]
# XDM_SERVER = 192.168.67.1
SERVER = 192.168.67.1
LDM_DIRECT = 192.168.67.1
SCREEN_01 = ldm
SCREEN_02 = xfreerdp -f --ignore-certificate --no-nla -k 0x00000415 -a
16 --plugin rdpsnd --data alsa --plugin drdynvc --data
tsmf:decoder:gststreamer --plugin rdpdr --data disk:usb:/media --
192.168.0.4
SCREEN_03 = rdesktop -f -k pl -a 16 -r sound:local -r disk:usb=/media
192.168.0.4
SCREEN_06 = xterm
SCREEN_07 = shell
# XRANDR_MODE_0 = 1920x1200
# XSERVER = nv
# X_MONITOR_OPTION_01 = "1920x1200_60.00" 163.25 1920 2056 2256 2592
1200 1203 1245 -hasync +vsync
# X_MODE_0 = 1920x1200
# X_HORYZSYNC = 30-80
# X_VERTEREFRESH = 56-75

After thin client rebooting I couldn't see any changes. There is no any
other SCREEN accessible like LDM (SCREEN_01). After trying screen change
(Ctrl+Alt+F2) I can see black screen with blanking pointer only. There
is no possible to return SCREEN_01. I can return to LDM using Ctrl+Alt
+F7

Let me add that I installed rdesktop and xfreerdp packages using next
commands:

# setarch i386 chroot /opt/ltsp/i386
<LTSP epel-6-i386> # mount /proc
<LTSP epel-6-i386> # yum install rdesktop xfreerdp
<LTSP epel-6-i386> # umount /proc
<LTSP epel-6-i386> # exit

Using LTSP 5.1 lts.conf was placed in /var/lib/tftpboot/ltsp/i386

Now I can read in the first line of lts.conf file "If using NFS,
lts.conf goes in /opt/ltsp/<arch>/etc/lts.conf." So I made symbolic
link /var/lib/tftpboot/ltsp/i386/lts.conf -> /opt/ltsp/i386/etc/lts.conf

and noting.

Could anybody advice me what I wrong?

Best regards,
Radek

Barry Cisna

2013-07-02 12:09:47 UTC

Permalink

Radek,

In your lts.conf file. For your SCREEN_03= you need an " at each end of
your config for SCREEN_03.

Example: SCREEN_03= "rdesktop -f -k pl -a 16 -r sound:local -r
disk:usb=/media 192.168.0.4"
#Note the two " beginning and end here.

Also,,,there are some known problems with xfreerdp that gives some odd
stuff on Windows Sever 2008.

Barry

Barry Cisna

2013-07-02 17:17:49 UTC

Permalink

Radek,

What may be your problem is if HOME is unset xfreerdp segfaults.

Open /opt/ltsp/i386/usr/share/ltsp/screen.d/xfreerdp

At almost the top of this file You will see a line ..
. /usr/share/ltsp/screen-x-common
Below this line you should have ,,,
export HOME=${HOME:-/root}

If the above line is not there,, add it,,SAVE

reboot your TC,,
Your rdesktop will work on the TC now.

Take Care,
Barry

Radek Bursztynowski

2013-07-02 19:38:02 UTC

Permalink

Barry,

Many thanks for your help. Unfortunately nothing works.

Let me set in order my lts.conf manipulations.
I can add, that I tested my lts.conf LTSP 5.1. All work fine excluding
Fedora 10 image, but let's forget about it now. It is the reason that I
copy parts of lts.conf from LTSP 5.1 to lts.conf LTSP 5.9.

1)
I test LTSP 5.9 now (thin client i386 epel6).
Thin client boots and I can log in. But what is strange - every time
after booting thin client I write user login name and push Enter to move
to password line, login screen reloads. Sometime I must repeat twice or
three times procedure when I can write password and log in.

The resolution of the screen is 1680x1050 only. But thin client works
fine (I solved my troubles with two NICs and network).

After log off I try to switch to Windows 7 screen (xfreerdp). I can see
black screen with blanking pointer. I checked my lts.conf. All line with
xfreerdp command uses " ".
Next I assured myself
regarding /opt/ltsp/i386/usr/share/ltsp/screen.d/xfreerdp.
export HOME=${HOME:-/root} line exists.
I remember that this change
in /opt/ltsp/i386/usr/share/ltsp/screen.d/xfreerdp file was necessary in
LTSP 5.1, but 5.9 corrected this bug.

I try to come back to SCREEN_01 with LDM. I can see black screen with
the following information:

"
Traceback (most recent call last): File "/usr/sbin/firstboot", line 168,
in <module> config.front.end.start()

File "/usr/lib/python2.6/site-packages/firstboot/xfrontend.py", line 64,
in start with open ("/etc/sysconfig/i18n", "r") as f: 10 Error: [Error
2] No such file or directory.
"

2)
Still LTSP 5.9. I added (from my backup) thin client image from LTSP 5.1
to /opt/ltsp and /var/lib/tftpboot directory and configured ltsp-dhcpd.
Thin client boots, but I can see last text screen before login screen.

3)
The behaviour of LTSP described in 1) point is the same like with LTSP
5.1 and Fedora 10 image. It means that I can see on SCREEN_01 LDM, but I
can't reach Windows screen (rdesktop) on next screen described in
lts.con file.
Somebody could ask wile Fedora 10 image? Fedora 10 image cooperates with
very old machine (K6 III 400) with GeForce 2 MX 200.

So I still looking for the solution.

Best regards,
Radek

---

Post by Barry Cisna
Radek,
What may be your problem is if HOME is unset xfreerdp segfaults.
Open /opt/ltsp/i386/usr/share/ltsp/screen.d/xfreerdp
At almost the top of this file You will see a line ..
. /usr/share/ltsp/screen-x-common
Below this line you should have ,,,
export HOME=${HOME:-/root}
If the above line is not there,, add it,,SAVE
reboot your TC,,
Your rdesktop will work on the TC now.
Take Care,
Barry
_______________________________________________
K12OSN mailing list
https://www.redhat.com/mailman/listinfo/k12osn
For more info see <http://www.k12os.org>

Radek Bursztynowski

2013-07-02 22:01:10 UTC

Permalink

I tried all evening. Still nothing. In my opinion thin client couldn't
load lts.conf. I don't know why.

Best regards,
Radek

Barry Cisna

2013-07-03 14:31:14 UTC

Permalink

Radek,

rename your /opt/ltsp to /opt/ltspOLD
rename /var/lib/tftpboot to /var/lib/tftpbootOLD
Do a fresh ltsp-client-build
You will have to copy /var/lib/tfpbootOLD/pxelinux.0 & pxelinux.cfg to
your new /var/lib/tftpboot/i386

Also I have experinced the login hit and miss with updateding,,
What that is,,if you installed icedtea-web for 'java-plugin' this is not
leaving an 'netx/lock file in the /tmp dir this resolves the prob until
a client is rebooted and the same user logs in two times???

Barry

Radek Bursztynowski

2013-07-03 18:27:14 UTC

Permalink

Barry,

Thanks again. I will do it tomorrow.
Today I can say that I found few differences between the newest lts.conf
manual (1)
http://manpages.ubuntu.com/manpages/raring/en/man5/lts.conf.5.html

and older (2)

http://www.bursztynowski.waw.pl/ftp/linux/LinuxTerminalServerProject/LTSPManual.pdf

Regarding (1) - I found this web page trucking K12Linux.
Regarding (2) - I fount this pdf file few mounts ago (I don't remember
where), but I downloaded it and added to my server.

I support myself using pdf file, but I see that I should read carefully
new web page and postpone my activity to ending reading.

Best regards,
Radek

----

Post by Barry Cisna
Radek,
rename your /opt/ltsp to /opt/ltspOLD
rename /var/lib/tftpboot to /var/lib/tftpbootOLD
Do a fresh ltsp-client-build
You will have to copy /var/lib/tfpbootOLD/pxelinux.0 & pxelinux.cfg to
your new /var/lib/tftpboot/i386
Also I have experinced the login hit and miss with updateding,,
What that is,,if you installed icedtea-web for 'java-plugin' this is not
leaving an 'netx/lock file in the /tmp dir this resolves the prob until
a client is rebooted and the same user logs in two times???
Barry
_______________________________________________
K12OSN mailing list
https://www.redhat.com/mailman/listinfo/k12osn
For more info see <http://www.k12os.org>

Radek Bursztynowski

2013-07-03 19:33:02 UTC

Permalink

Sorry for big avalanche of my questions, but K12Linux is very important
to me, and I must manage new version K12.

My few next doubts.

Using chroot mechanism I try to manage several thin client images.
/opt/ltsp/i386 and /var/lib/tftpboot/ltsp/i386 directories belong to
epel-6-i386 ltsp-build-client (LTSP 5.9)

/opt/ltsp/i386-fed14 and /var/lib/tftpboot/ltsp/i386-fed14 belong to
Fedora 14 image which I restored from my backup LTSP 5.1. I note that
original /opt/ltsp/i386-fed14/etc/ltsp_chroot file encloses
LTSP_CHROOT=/opt/ltsp/i386 line, not LTSP_CHROOT=/opt/ltsp/i386-fed14
while I expected that ltsp-build-client --release 14 --chroot i386-fed14
create LTSP_CHROOT=/opt/ltsp/i386-fed14, not LTSP_CHROOT=/opt/ltsp/i386
line. But everything worked fine with LTSP 5.1.

The question is: which line is regular?

And the second doubt.

/opt/ltsp/i386-fed14/etc/sysconfig/mkinitrd file encloses

rootdev="192.168.0.254:/opt/ltsp/i386"

Still /opt/ltsp/i386 directory, not /opt/ltsp/i386-fed14

and rootdev is 192.168.0.254 while 192.168.0.254 is my network gateway,
not my server IP address. My server address is 192.168.0.1

The question is: which line is regular:
rootdev="192.168.0.254:/opt/ltsp/i386"
or
rootdev="192.168.0.1:/opt/ltsp/i386-fed14" ?

I checked /opt/ltsp/i386/etc/sysconfig/mkinitrd (epel-6-i386) and this
line is:
rootdev="server:/opt/ltsp/i386"

I expect that "server" is variable which we can describe in lts.conf
like: SERVER=192.168.67.1. Isn't it?
So ltsp-build-client with LTSP 5.9 cleates regular rootdev line. Isn't
it?

Best regards,
Radek

----

Burke Almquist

2013-07-04 05:20:19 UTC

Permalink

Radek, did you go through the /etc/ltsp folder and edit all the files? You really need to do that before running ltsp-build-client.

Radek Bursztynowski

2013-07-10 19:21:15 UTC

Permalink

Hello,

(Me again...).

Thanks again for all advices. I solved a lot of (my) problems, but not
all. Now LTSP 5.4.4-23 and epel-6-i366 client work but I try to solve
next problems:

1. I defined three SCREEN_01 to SCREEN_03 in my lts.conf. All work fine,
but I don't know why every time thin client boots SCREEN_03 the first
while I expect SCREEN_01 the first time. How to change the order of
SCREENS ?

2. xfreerdp still supports mono sound only. Perhaps next version of this
package will solve this problem :(.

3. I added older version of client (Scientific Linux 6.1). Thin client
boots but I can reach login window using Ctrl+Alt+F7 only while I copied
lts.conf from my epel-6-i386 thin client (see point 1). It seems that
thin client doesn't see lts.conf. I don't know why. Identical behaviour
is with Fedora 11 thin client image. I can forget about SL 6.1 image,
but I need Fedora 11 (i586 arch.).

Perhaps somebody could help me.

Best regards,
Radek

---

William Fragakis

2013-07-11 20:35:51 UTC

Permalink

Radek,
This may be of no assistance but I seem to recall in an earlier post
that one of your "true" statements in the lts.conf had a typo (iirc,
TRUE was misspelled).

At one time ltsp was quite sensitive to typos in lts.conf and would
ignore the entire config if it ran into any errors. Perhaps that's no
longer the case but it may be worthwhile to look it over.

Regards,
William (who spent way too much time looking for lost semi-colons in
perl scripts)

Message: 1
Date: Wed, 10 Jul 2013 21:21:15 +0200
To: "Support list for open source software in schools."
Subject: Re: [K12OSN] No reaction following lts.conf changes
Content-Type: text/plain; charset="US-ASCII"
Hello,
(Me again...).
Thanks again for all advices. I solved a lot of (my) problems, but not
all. Now LTSP 5.4.4-23 and epel-6-i366 client work but I try to solve
1. I defined three SCREEN_01 to SCREEN_03 in my lts.conf. All work fine,
but I don't know why every time thin client boots SCREEN_03 the first
while I expect SCREEN_01 the first time. How to change the order of
SCREENS ?
2. xfreerdp still supports mono sound only. Perhaps next version of this
package will solve this problem :(.
3. I added older version of client (Scientific Linux 6.1). Thin client
boots but I can reach login window using Ctrl+Alt+F7 only while I copied
lts.conf from my epel-6-i386 thin client (see point 1). It seems that
thin client doesn't see lts.conf. I don't know why. Identical behaviour
is with Fedora 11 thin client image. I can forget about SL 6.1 image,
but I need Fedora 11 (i586 arch.).
Perhaps somebody could help me.
Best regards,
Radek
---