hi cuneyt
cuneytm schrieb:
>
> Sorry for the length of this post as i converted it from my notes while
> playing with openthinclient.
> Rest assured, i would be happy to compile them under How To or such for the
> Wiki pages.
>
that would be cool!
> Following are the list of questions. Thank you in advance for your
> attention.
>
you're welcome :-)
> How to centrally set (as Skeleton/Default) gnome-default-applications ->
> Mail Reader COMMAND field to a shell script path like
> /bin/webMail_compose.sh so that we can launch the webmail for all mailto:
> links?
>
if you change the mail reader command via gnome-default-applications-properties
and terminate your session by logging out your configuration is written to:
/home/tcos/.gconf/desktop/gnome/url-handlers/mailto/%gconf.xml
this file holds your configuration changes and could look like this:
<?xml version="1.0"?>
<gconf>
<entry name="command" mtime="1220956899" type="string">
<stringvalue>/bin/webMail_compose.sh %s</stringvalue>
</entry>
</gconf>
the easiest way to make this a default for all users/thin clients is to create
the following folder on your openthinclient server:
<INSTALLPATH>\server\default\data\nfs\home\_USER_OVERWRITE_\.gconf\desktop\gnome\url-handlers\mailto
and copy the above stated file "%gconf.xml" into it.
> What is the best way to inject this shell script, say webMail_compose.sh to
> the Core so it will be accessible in all and future thinclients.
>
the quick and dirty way would be to copy your shell script in the
"_USER_OVERWRITE_" directory as well and set the mail reader command to
something like:
/home/tcos/<PATH TO YOUR SCRIPT IN _USER_OVERWRITE_>/webMail_compose.sh
the proper way would be to create a separate package (for example "webmail")
and let it handle this. let's say you create a package via:
tcos_genpackage webmail
this will create the following files and directories for you:
webmail/
webmail/webmail-0.0.1
webmail/webmail-0.0.1/debian
webmail/webmail-0.0.1/debian/changelog
webmail/webmail-0.0.1/debian/compat
webmail/webmail-0.0.1/debian/control
webmail/webmail-0.0.1/debian/dirs
webmail/webmail-0.0.1/debian/rules
webmail/webmail-0.0.1/debian/docs
webmail/webmail-0.0.1/schema
webmail/webmail-0.0.1/schema/application
webmail/webmail-0.0.1/schema/application/webmail.xml
webmail/webmail-0.0.1/tcos
webmail/webmail-0.0.1/tcos/launcher
webmail/webmail-0.0.1/tcos/launcher.icon
webmail/webmail-0.0.1/tcos/webmail.desktop
webmail/webmail-0.0.1/webmail
as your webMail_compose.sh script is not a typical application (with launcher
and desktop icons...) and you don't need any configuration options (yet?) you
can delete the following files and directories:
webmail/webmail-0.0.1/schema/application
webmail/webmail-0.0.1/tcos/launcher
webmail/webmail-0.0.1/tcos/launcher.icon
webmail/webmail-0.0.1/tcos/webmail.desktop
so it a "find webmail" will have the following output:
webmail/webmail-0.0.1
webmail/webmail-0.0.1/debian
webmail/webmail-0.0.1/debian/changelog
webmail/webmail-0.0.1/debian/compat
webmail/webmail-0.0.1/debian/control
webmail/webmail-0.0.1/debian/dirs
webmail/webmail-0.0.1/debian/rules
webmail/webmail-0.0.1/debian/docs
webmail/webmail-0.0.1/schema
webmail/webmail-0.0.1/tcos
webmail/webmail-0.0.1/webmail
then create the directory:
webmail/webmail-0.0.1/webmail/bin
and copy your script into it:
webmail/webmail-0.0.1/webmail/bin/webMail_compose.sh
if you would build and install this package now, your script would be available
for the OS in /opt/webmail/bin/webMail_compose.sh
so your script is included but you still need to tell gnome how to use it. for
this purpose i have to go into greater detail.
you can create some "magic" directories inside the "webmail/webmail-0.0.1/tcos"
directory to put additional scripts in. they will be executed by run-parts (see
man run-parts) at different points in time:
rcS.d
- executed right after init starts
rc2345.d
- executed when switching to runlevel 2
rc.local
- executed at the end of the multiuser runlevel.
PostLogin
- executed right after gnome login (home dir mounted and gconfd started)
PostSession
- executed on gnome logout
as you wish to modify gconf settings you should create the directory:
webmail/webmail-0.0.1/tcos/PostLogin
and create a setMailCommand.sh script to put it there:
webmail/webmail-0.0.1/tcos/PostLogin/setMailCommand.sh
this script should modify the gconf-database or create the above stated
".../%gconf.xml" file. hint: have a look at the desktop package on how to
modify the gconf-database with gconftool-2.
> How to centrally (as Skeleton/Default) register MIME types with Firefox for
> all thinclients. Is there a location on the openthinclient server that we
> can drop the defaults so that it will be copied to every new thinclient user
> created?
>
there are different files/directories for handling mime times: the file
/etc/mailcap and the directory /usr/share/applications containing the *.desktop
files with its /usr/share/applications/mimeinfo.cache.
usually an application adds its capabilities to these files/this folder. have a
look at the evince package for example. it has a mime script installed here:
/opt/evince/tcos/rc2345.d/mime
this script
- modifies the /etc/mailcap with entries like:
application/pdf; /opt/evince/bin/evince '%s'; nametemplate=%s.pdf
...
- adds the evince.desktop file to the /usr/share/applications folder
- and modifies the /usr/share/applications/mimeinfo.cache like:
application/pdf=evince.desktop
...
> How to facilitate Single Sign On with Web Applications? I understand
> environment variables USER and TCOS_TOKEN keeps the uname:pwd upon
> thinclient login.
>
that's right.
> Can we pass the USER TCOS_TOKEN environment variables to the Firefox App as
> URL, say create new firefox application and set launch URL to
> http://intranet/login.aspx?user=$USER&pwd=&TCOS_TOKEN ?
>
almost. you have to bash-escape if you ar not quoting:
http://intranet/login.aspx\?user=$USER\&pwd=$TCOS_TOKEN
loggin in as user/pw: foobar/foobar would generate the following request:
http://intranet/login.aspx?user=foobar&pwd=000767010901040217
> Assuming we passed that to the webserver login page, how to decode the
> TCOS_TOKEN? is it encrypted with publicly available algorithm or custom?
>
don't tell anyone:
it's the original highly sophisticated heavily encrypted and unbreakable citrix
ica-client password algorithm reverse engineered ;-)
have a look at the sso-tcos source package or use
/opt/sso-tcos/bin/sso-tcos-auth for getting the password in plain text to
scramble it however you like.
for example use:
http://intra.levigo.de/login.aspx\?user=$USER\&pwd=$(/opt/sso-tcos/bin/sso-tcos-auth)
to pass pwd in plain text.
> How to enable Show Memory graph in taskbar, next to cpu and network? Is
> there a security or other concerns that GNOME-MONITOR is disabled/removed?
> As more applications (multiple firefox windows, VLC windows) will be running
> locally, do you think giving end-user to see and kill his (user) processes
> via GNOME-MONITOR is advisable?
>
this answer is simple:
it's just not included yet.
> How to enable/show GNOME-VOLUME CONTROL? It complains the file is missing
> when you dbl-click it. Is there a reason for disabling this, like the
> GNOME-MONITOR?
>
same here
> How to set (as Skeleton, default) GNOME desktop defaulting to
> "low-resources" that disables animation and show-contents-on-drag for all
> current and future thinclient users?
>
see above or my reply to "Lame Openchrome driver" at 7th sept. 2008
> How to Add new printer drivers? Say the driver is not listed in default
> printers dropdown and we located the driver from vendor's page -> CANON IRc
> 5xxx linux .deb files on canon site. What is the best way to include this
> printer to the base and show under the dropdown selection of OpenThinClient
> Manager?
>
this is on to-do. the printer package will be updated to include this.
in the meantime you can try the generic postscript driver for you canon printer.
> Being a complete newbie to Linux and CUPS, do we need add special parameters
> (schema field) when adding new CUPS printer? Can you give a generic
> simplistic schema/parameters that one would use to add the CUPS printer
> under Manager.
>
it will probably be implemented like that: you download a cups printer driver
and enter the path to this driver. this should be quite generic.
> How to create default folders (as Skeleton, defaults) on each thinclient
> user's desktop? for ex: a Download folder on each user's desktop so that
> documents downloaded from net will be saved to this folder - as part of
> company policy etc. reasons. Is there a way or place to create this
> folder(s) when a new user created?
>
just create the folder in the mentioned "_USER_OVERWRITE_" directory
> How to set (as skeleton, defaults) the settings of FireFox browser for all
> current and future thinclient users? I noticed if i root in the thinclient
> via xterm, i can locate /etc/skel/ folder which seems to hold the defaults
> for firefox but i cant trace that folder on the openthinclient server. is
> this created on the fly? where can we store the defaults for firefox and/or
> OpenOffice to be inherited?
>
> The same goes for OpenOffice, is there a /etc/skel/ folder for openOffice
> settings as well that will be inherited for all users?
>
/etc/skel/ is included inside the base.sfs squashfs-image and not accessible on
the openthinclient server .
for now use the "_USER_OVERWRITE_" directory as well because the firefox
defaults included in /etc/skel are a kind of deprecated.
> As i had a number of issues with Evince PDF viewer opening big files (>6mb),
> i was wondering if an update to evince will solve that issue or adding Adobe
> PDF Reader plugin to Firefox is a good idea in terms of CPU/Mem usage and
> footprint?
>
maybe you are running out of RAM. if you download a PDF it will be saved in
/tmp which is a RAM disk. please paste the output of the command "free" in a
running session to see if it's a evince-bug or not.
adobe reader is quite bloated compared to evince.
> I managed to install the flash plug-in while i was playing with the settings
> of Firefox (without realizing) but i cant seem to reproduce that. Is there a
> particular reason on why the online Flash plug-in installation fails ?
>
that's interesting. AFAIK there is no working online flash plug-in installer
for linux that works at all.
it would be quite interesting to know how you got the flash-plugin working
(without using any shell or other helper apps).
> I managed to connect a Logitech QuickCam Pro 4000 and tested online
> conferencing via Flash plugin with success. However after few days, the
> camera image gone all fuzzy with diagonal lines. The cam is fine and works
> well in windows. But curious what might cause a sudden corruption of the
> video image from it.
>
so now it's always fuzzy with diagonal lines?
> Is there a small tool out there, which can be embedded to openThinClient, to
> adjust usb video-cam settings? Or any other generic tool that can be used to
> run diagnosis for the webcam?
>
i don't know ;-(
> I noticed openthinclient/ubuntu didnt detect the Creative Live! camera (that
> we have tons of them in the office) but the QuickCam pro 4000.
> Is there a list of USB Cameras thats supported and known to work with the
> version of openthinclient build of ubuntu?
>
probably all supported by ubuntu dapper.
> Can we assign quotas and/or warning (i.e. clear your tmp folder, you are
> reaching your local storage limit ...) to users' NFS folders?
>
well /tmp (the linux temp folder) is non-persistent and gets cleaned after the
user logs out.
the home dir is another story. to implement real quotas for the java nfs server
would be some work but you could use a linux nfs server to achieve this.
on the other hand it would be easy to mount fixed sized loop back images as
home directories (not implemented yet).
> When do we delete the temp folfder of user? As it will constantly grow,
> wondering if there is a daemon or such that wipes out the tmp files and
> folder.This question is purely related to long term management and up-keep
> of the openthinclient server and NFS store.
>
see above
> Is there a "centralized" logging system that can capture the stuff going
> wrong on user's thinclient? something like ...\thinClient_Logs\username.log
> which can be configured with detail of logging?
>
right know you can right-click on the desired thin-client to see it's logs.
> What is the best approach to setup a Fail-Over thinclient Server ? As its a
> single point of failure where each client depends on, what will be the best
> approach to setup fail-over openthinclient servers?
>
as everything is stored in a single folder you can easily backup this folder or
synchronize it to an other machine. this machine could do a kind of cold
failover.
we have already some specs of implementing real failover on server side but
right now it's not top priority. there will be support for local boot/local
storage (flash disk/USB...) implemented first to circumvent a single point of
failure.
> I noticed the warning about configuring the DHCP server (running on seperate
> server). We are already using the DHCP server for booting VoIP phones in
> the network and just wanna make sure if the following settings of dhcpd.conf
> will work OK without problems for openthinclient server?
>
> example dhcpd.conf file:
>
> subnet 192.168.2.0 netmask 255.255.255.0 {
> range 192.168.2.151 192.168.2.199;
> default-lease-time 21600;
> max-lease-time 43200;
> option routers 192.168.2.1;
> option subnet-mask 255.255.255.0;
> option domain-name "domain.com";
> option domain-name-servers 192.168.2.2;
> option tftp-server-name "voip.domain.com";
> option ntp-servers 192.168.2.2;
> }
>
this should be fine.
cheers,
martin
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
The Open Source Thin Client Solution http://openthinclient.org
[email protected]
https://lists.sourceforge.net/lists/listinfo/openthinclient-user
