I'm using version 4.1.1 K12LTSP<br>
<br>
I'm having some trouble getting the Citrix client to come up
properly. I used the script you sent Gideon but I get nothing by
the "gray sceen" I can see that X is coming up ok but where can I
look to get more information about what is going
wrong? I can look in the /tmp/info directory on the
terminal but there is not much in there. What I'd really
like to see is a file someplace that tells me what was executed at the
end of this whole process.<br>
<br>
Here is a copy of my citrix-screen file:<br>
#!/bin/sh<br>
#<br>
# citrix<br>
#<br>
# citrix screen script for the linux terminal server project.<br>
# This script lives in the /opt/ltsp/i386/etc/screen.d directory<br>
#<br>
# Call it through lts.conf with the `SCREEN_xx = citrix` option.<br>
#<br>
# You can pass options to citrix 2 different ways.<br>
#<br>
# 1) Place all of the options you want after the 'citrix' setting<br>
# on the screen_script.<br>
#<br>
# For example:<br>
#<br>
# SCREEN_01 = citrix -u jam <a href="http://w2kserver.ltsp.org">w2kserver.ltsp.org</a><br>
#<br>
#<br>
# 2) Place the citrix options in the CITRIX_OPTIONS option<br>
# and the name or IP address of the rdp server in<br>
# the CITRIX_SERVER option.<br>
#<br>
# For example:<br>
#<br>
# CITRIX_OPTIONS = "-f -u jam"<br>
# CITRIX_SERVER = <a href="http://w2kserver.ltsp.org">w2kserver.ltsp.org</a><br>
# SCREEN_01 = citrix<br>
#<br>
<br>
PATH=/bin:$PATH; export PATH<br>
. /etc/ltsp_functions<br>
<br>
#<br>
# Get the lts.conf entries<br>
#<br>
eval `/bin/getltscfg -a`<br>
<br>
CITRIX_OPTIONS=${CITRIX_OPTIONS:-""}<br>
<br>
reg_info CITRIX_SERVER<br>
reg_info CITRIX_OPTIONS<br>
<br>
TTY=`/usr/bin/basename \`/usr/bin/tty\``<br>
XFCFG=/tmp/XF86Config.${TTY}<br>
export TTY<br>
<br>
CITRIX_OPTIONS="${CITRIX_OPTIONS} $* ${CITRIX_SERVER}"<br>
<br>
# <br>
# Setup the DISP variable<br>
# <br>
export DISP=:$(expr ${TTY} - 1).0<br>
<br>
################################################################################<br>
#<br>
# Setup the XF86Config file<br>
#<br>
<br>
XSERVER=${XSERVER:-"auto"}<br>
<br>
if [ "${XSERVER}" = "auto" ]; then<br>
echo "Scanning for video card"<br>
XSERVER=`/sbin/pci_scan /etc/vidlist`<br>
if [ -z "${XSERVER}" ]; then<br>
echo<br>
echo " ERROR: Auto probe of the video card failed !"<br>
echo
" You need to specify
the proper X server in lts.conf"<br>
echo<br>
echo -n "Press <enter> to continue "<br>
read CMD<br>
exit 1<br>
fi<br>
fi<br>
<br>
if [ "${XSERVER}" = "i810" ]; then<br>
if [ ! -f /tmp/i810_loaded ]; then<br>
modprobe agpgart<br>
>/tmp/i810_loaded<br>
fi<br>
fi<br>
<br>
if [ ! -z "${XF86CONFIG_FILE}" ]; then<br>
#<br>
# If XF86CONFIG_FILE is defined in the lts.conf file, then<br>
# it points to an XF86Config file that is pre-made for a workstation<br>
#<br>
if [ -f /etc/${XF86CONFIG_FILE} ]; then<br>
cp /etc/${XF86CONFIG_FILE} ${XFCFG}<br>
else<br>
echo<br>
echo "Error! - ${XF86CONFIG_FILE} - File not found!"<br>
echo<br>
fi<br>
else<br>
#<br>
# Build the XF86Config file from entries in the lts.conf file<br>
# If it starts with 'XF86_', then we use XFree86 3.3.6. Otherwise,<br>
# we use Xorg<br>
#<br>
case ${XSERVER} in<br>
<br>
XF86_*) /etc/build_x3_cfg ${XSERVER} >${XFCFG}<br>
;;<br>
<br>
*) /etc/build_x4_cfg ${XSERVER} >${XFCFG}<br>
;;<br>
esac<br>
fi<br>
<br>
################################################################################<br>
#<br>
# Figure out how to run the X server<br>
#<br>
<br>
case ${XSERVER} in<br>
<br>
XF86_*) XBINARY="${XSERVER}"<br>
XOPTS=""<br>
;;<br>
<br>
Xvesa) XBINARY="Xvesa"<br>
case "${X_MODE_0}" in<br>
1280x1024) XOPTS="-shadow -mode 0x011A"<br>
;;<br>
1024x768) XOPTS="-shadow -mode 0x0117"<br>
;;<br>
800x600) XOPTS="-shadow -mode 0x0114"<br>
;;<br>
640x480) XOPTS="-shadow -mode 0x0111"<br>
;;<br>
*)
XOPTS="-shadow -mode 0x0117"<br>
;;<br>
esac<br>
;;<br>
<br>
*) XBINARY="Xorg"<br>
XOPTS=""<br>
;;<br>
esac<br>
<br>
ACCESS_CONTROL=${DISABLE_ACCESS_CONTROL:-"N"}<br>
if [ "${ACCESS_CONTROL}" = "Y" ]; then<br>
ACC_CTRL="-ac"<br>
else<br>
ACC_CTRL=""<br>
fi<br>
<br>
clear<br>
echo<br>
echo<br>
echo<br>
echo<br>
echo<br>
echo<br>
echo<br>
echo<br>
echo<br>
echo<br>
echo<br>
echo<br>
echo -n
"
Press <enter> to Login "<br>
read<br>
<br>
if [ -w /proc/progress ]; then<br>
/usr/X11R6/bin/xinit
/usr/bin/citrix.wrapper
\<br>
-log
""
\<br>
${CITRIX_OPTIONS} \<br>
-- /usr/X11R6/bin/${XBINARY}\<br>
${DISP}
\<br>
-xf86config ${XFCFG} \<br>
vt${TTY} >/dev/null 2>&1<br>
else<br>
/usr/X11R6/bin/xinit
/usr/bin/citrix.wrapper
\<br>
-f
""
\<br>
${CITRIX_OPTIONS} \<br>
-- /usr/X11R6/bin/${XBINARY}\<br>
${DISP}
\<br>
-xf86config ${XFCFG} \<br>
vt${TTY}<br>
fi<br>
<br>
<br>
Here is the other relavent file citrix-wrapper:<br>
<br>
#!/bin/sh<br>
<br>
while true; do<br>
/usr/lib/ICAClient/wfcmgr "$@"<br>
done<br>
<br>
<br>
I know the client works because I can execute it manually from the command line on the server.<br>
<br>
Jack<br>
<br>
<br>
<br>
<br>
----------------------------------------------------------------------------------------------------------<br><br><div><span class="gmail_quote">On 3/17/06, <b class="gmail_sendername">Gideon Romm</b> <<a href="mailto:ltsp@symbio-technologies.com">
ltsp@symbio-technologies.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Jack-<br><br>No problem. If you can, please post your version of K12LTSP, just so
<br>any future person searching these archives with the same problem will be<br>able to find the solution easier.<br><br>Cheers,<br><br>-Gideon<br><br>On Fri, 2006-03-17 at 08:46 -0500, Jack Palmadesso wrote:<br>> Thanks a bunch. You must have been reading my mind or something
<br>> because I am very interested in these wrapper scripts. I have been<br>> lucky enough to demo LTSP for the company I work for and I'd like to<br>> have the ability to launch other applicatons like Citrix for example
<br>> for certain terminals. Some people want Linux, some want a Windows<br>> terminal server and some want Citrix. LTSP can fit the bill on all of<br>> these with a few servers and lots of old hardware nobody wants to use.
<br>><br>> Thanks again<br>> Jack<br>><br>> On 3/16/06, Gideon Romm <<a href="mailto:ltsp@symbio-technologies.com">ltsp@symbio-technologies.com</a>> wrote:<br>> I figured I'd just send them along to the list.
<br>><br>> 1. Back up your /opt/ltsp/i386/etc/screen.d/rdesktop file<br>> 2. Replace with the attached rdesktop-screen (remember to<br>> chmod 755)<br>> 3. place the rdesktop.wrapper
file<br>> in /opt/ltsp/i386/usr/bin (also,<br>> chmod 755)<br>><br>> Let 'er rip!<br>><br>> -Gideon<br>><br>> PS: Usual caveats about listening to some guy on the listserv
<br>> apply (in<br>> terms of the computers coming to life and destroying the world<br>> on<br>> you...)<br>><br>> On Thu, 2006-03-16 at 16:57 -0500, Gideon Romm wrote:
<br>> > Jack-<br>> ><br>> > This behavior has been changed since LTSP v. 4.1.1 (I'm not<br>> sure what<br>> > version you are using). In the latest version of LTSP, a
<br>> wrapper script<br>> > is called that launches rdesktop again when it dies, so that<br>> it does not<br>> > kill the xserver.<br>> ><br>> > I can dig up the wrapper script and send it to you if you
<br>> like. Or, if<br>> > you can, update to the latest version.<br>> ><br>> > Regards,<br>> ><br>> > -Gideon<br>> ><br>> > On Thu, 2006-03-16 at 15:37 -0500, Jack Palmadesso wrote:
<br>> > > Forget it. I now realize that it is nessasary to have<br>> "press enter to<br>> > > login" appear so as not to be constantly knocking on a W2k<br>> terminal
<br>>
> > servers door constantly. If a user get a terminal
server<br>> login but<br>> > > does not do anything for few minutes then the terminal<br>> server rightly<br>>
> > kicks the user off. when the user it kicked off it
would<br>> be "rude" to<br>> > > just have the server automatically try and go back to the<br>> login screen<br>> > > when nobody was probably at the terminal to begin with.
<br>> > ><br>> > > On 3/14/06, Jack Palmadesso <<a href="mailto:jack.palmadesso@gmail.com">jack.palmadesso@gmail.com</a>><br>> wrote:<br>>
> > I'm demoing
LTSP to managment here tommorow. Some<br>> of the<br>>
> > terminals
will go directly to a W2k3 Terminal<br>> server via the<br>>
> > setting in
"lts.conf" That works fine but just<br>> before X fires<br>>
> > up the
terminal prompts the user to "press enter<br>> to login".<br>>
> > Can I get
around this and just have the terminal<br>> go directly<br>>
> >
in? I'm not complaining but it would just be alot<br>> smoother to<br>>
> > have it
bypass that requirement. Anybody have any<br>> hints for<br>>
> > me on that
one? I'll be demoing on 4.4.1<br>> > ><br>> > > Thanks,<br>> > ><br>> > > Jack<br>> > ><br>> > ><br>> > > _______________________________________________
<br>> > > K12OSN mailing list<br>> > > <a href="mailto:K12OSN@redhat.com">K12OSN@redhat.com</a><br>> > > <a href="https://www.redhat.com/mailman/listinfo/k12osn">https://www.redhat.com/mailman/listinfo/k12osn
</a><br>> > > For more info see <<a href="http://www.k12os.org">http://www.k12os.org</a>><br>> ><br>> > _______________________________________________<br>> > K12OSN mailing list
<br>> > <a href="mailto:K12OSN@redhat.com">K12OSN@redhat.com</a><br>> > <a href="https://www.redhat.com/mailman/listinfo/k12osn">https://www.redhat.com/mailman/listinfo/k12osn</a><br>> > For more info see <
<a href="http://www.k12os.org">http://www.k12os.org</a>><br>> ><br>> ><br>> --<br>> --------------------------------------------------------<br>> Gideon Romm | Product R&D
<a href="mailto:gideon@symbio-technologies.com">gideon@symbio-technologies.com</a><br>><br>>
Symbio
Technologies
o:(914) 576-1205<br>>
134 North Ave, Suites
E&F
f:(914) 576-0944<br>>
New Rochelle, NY
10801 c:(914)
774-4691<br>><br>>
<a href="http://www.symbio-technologies.com">www.symbio-technologies.com</a><br>>
<a href="http://www.thesymbiont.com">www.thesymbiont.com</a><br>><br>><br>> _______________________________________________<br>> K12OSN mailing list<br>> <a href="mailto:K12OSN@redhat.com">
K12OSN@redhat.com</a><br>> <a href="https://www.redhat.com/mailman/listinfo/k12osn">https://www.redhat.com/mailman/listinfo/k12osn</a><br>> For more info see <<a href="http://www.k12os.org">http://www.k12os.org
</a>><br>><br>><br>><br>> _______________________________________________<br>> K12OSN mailing list<br>> <a href="mailto:K12OSN@redhat.com">K12OSN@redhat.com</a><br>> <a href="https://www.redhat.com/mailman/listinfo/k12osn">
https://www.redhat.com/mailman/listinfo/k12osn</a><br>> For more info see <<a href="http://www.k12os.org">http://www.k12os.org</a>><br>--<br>--------------------------------------------------------<br>Gideon Romm | Proud LTSP Developer
<br><a href="mailto:ltsp@symbio-technologies.com">ltsp@symbio-technologies.com</a><br><br>Support LTSP! Buy your hardware at:<br><br> <a href="http://www.DisklessWorkstations.com">www.DisklessWorkstations.com</a><br>
<a href="http://www.DisklessThinClients.com">www.DisklessThinClients.com</a><br><br><br>_______________________________________________<br>K12OSN mailing list<br><a href="mailto:K12OSN@redhat.com">K12OSN@redhat.com
</a><br><a href="https://www.redhat.com/mailman/listinfo/k12osn">https://www.redhat.com/mailman/listinfo/k12osn</a><br>For more info see <<a href="http://www.k12os.org">http://www.k12os.org</a>><br></blockquote></div>
<br>