On 11/09/2014 05:03, Vagrant Cascadian wrote:
> On 2014-09-10 14:39:21 -0500, Denis Croombs wrote:
>> when we do a vulnerability scan it tells us that it is finding an x
>> server on each pxe booted device iPhone using port 6007/tcp.
> Thanks for reporting the issue, we didn't use the "-nolisten tc
On 2014-09-10 14:39:21 -0500, Denis Croombs wrote:
> when we do a vulnerability scan it tells us that it is finding an x
> server on each pxe booted device iPhone using port 6007/tcp.
Thanks for reporting the issue, we didn't use the "-nolisten tcp" flag
when starting the X server. I've fixed this
The X server is always listening for client apps to connect up and display
stuff.
Jim.
On Wed, Sep 10, 2014 at 4:46 PM, Vagrant Cascadian
wrote:
> On 2014-09-10 15:10:14 -0500, Vagrant Cascadian wrote:
> > I haven't yet verified for myself if 6007 is open in either the default
> > or LDM_DIRECT
On 2014-09-10 15:10:14 -0500, Vagrant Cascadian wrote:
> I haven't yet verified for myself if 6007 is open in either the default
> or LDM_DIRECTX case, but will do so shortly...
Seems to be an open port with or without LDM_DIRECTX, starts up as soon
as LDM is running.
I'm not sure what *exacty* X
On 2014-09-10 14:39:21 -0500, Denis Croombs wrote:
> Hi, we have some lisp servers
Wow, Lisp! Er, LTSP. :)
> and pc's pxe booting as thin long-running all apps on the ltsp server,
> but when we do a vulnerability scan it tells us that it is finding an
> x server on each pxe booted device iPhone
By default, all of the X traffic is tunneled through the ssh connection.
ssh will connect to the X server on a standard 600x range port, but it
should be doing it on the loopback interface (127.0.0.1).
But, the Xserver is probably still listening on the public interface
(usually something like
Hi, we have some lisp servers and pc's pxe booting as thin long-running all
apps on the ltsp server, but when we do a vulnerability scan it tells us that
it is finding an x server on each pxe booted device iPhone using port 6007/tcp.
I believed this connection between the pc and the server was ov
That did it. Works well. You can commit it upstream.
2009/6/5 Vagrant Cascadian :
> On Fri, Jun 05, 2009 at 04:18:43PM +0200, Peter Stein wrote:
>> I have a solution now. I commented something out in
>> /usr/share/ltsp/screen-x-common the prevented ldm from starting up.
> ...snip...
>
>> This mean
On Fri, Jun 05, 2009 at 04:18:43PM +0200, Peter Stein wrote:
> I have a solution now. I commented something out in
> /usr/share/ltsp/screen-x-common the prevented ldm from starting up.
...snip...
> This means it is not verified that xfs is online, but nc -w 5 $SRV
> 7100 gave no result than waitin
I have a solution now. I commented something out in
/usr/share/ltsp/screen-x-common the prevented ldm from starting up.
get_xfs_settings() {
# set default font path
# use XFS_SERVER if defined, otherwise
# attempt to use servers passed on commandline
if boolean_is_true "$USE_XFS"
On Thu, 2009-06-04 at 22:13 +0200, Peter Stein wrote:
> And what means: "Make available"? That is of course on possibility. If
> I have the fonts in the chroot - how to tell X that it should use
> those?
I added them to the Type1 font directory and made sure the fonts.dir and
fonts.scale were corr
And what means: "Make available"? That is of course on possibility. If
I have the fonts in the chroot - how to tell X that it should use
those?
2009/6/4 Andreas J Guelzow :
> On Thu, 2009-06-04 at 21:54 +0200, Peter Stein wrote:
>
>> Does anyone of you have an idea how to solve the problems mentio
On Thu, 2009-06-04 at 21:54 +0200, Peter Stein wrote:
> Does anyone of you have an idea how to solve the problems mentioned
> above or how to add a font path? This is a fundamental problem for
> everyone intending to use mathematica.
>
While the following doesn't answer your question, we "simply
As we switched to LTSP of Ubuntu 9.04 the way X is configured has
changed. Now you have a bunch of scripts in
/usr/share/ltsp/screen-session.d for X configuration. That makes it
very difficult for me to add a font path. I have no idea how to do
that. I still do not understand the way X is configure
Did you remeber X_CONFIGURE=True?
// Appiah
On Tue, Feb 3, 2009 at 11:14 AM, SZABO Zsolt wrote:
> How should one setup DPMS options such STANDBY SUSPEND OFFTIME in lts.conf
> (for ltsp 5)?
>
> The following does not work for me:
> X_DPMS_STANDBYTIME = 5
> X_DPMS_SUSPENDTIME = 10
> X
whilst using kiwi-ltsp, i have managed to get the two boot processes
working, but have issues with X starting. i get a login prompt but the
client then keeps flashing between login prompt and tty7 the error message
on ttty7 is
"xauth: creating new authority file /var/run/ldm-xauth-OgDRFLNBd"
whe
Le mardi 03 février 2009 11:14:44 SZABO Zsolt, vous avez écrit :
> How should one setup DPMS options such STANDBY SUSPEND OFFTIME in lts.conf
> (for ltsp 5)?
>
> The following does not work for me:
> X_DPMS_STANDBYTIME = 5
> X_DPMS_SUSPENDTIME = 10
> X_DPMS_OFFTIME = 15
> (though
How should one setup DPMS options such STANDBY SUSPEND OFFTIME in lts.conf
(for ltsp 5)?
The following does not work for me:
X_DPMS_STANDBYTIME = 5
X_DPMS_SUSPENDTIME = 10
X_DPMS_OFFTIME = 15
(though it was originally setup for ltsp4.2, AFAIK)
The /etc/X11/xorg.conf does not co
On Saturday 08 November 2008 14:12:20 ltsp-discuss-
[EMAIL PROTECTED] wrote:
> I have the following problem: the size of the fonts of certain web
> pages is too small in firefox... setting the default fontsize to a larger
> value does not help because the appearance of such pages are controlled
> v
I have the following problem: the size of the fonts of certain web
pages is too small in firefox... setting the default fontsize to a larger
value does not help because the appearance of such pages are controlled
via styles (i.e. the fontsizes are set explicitly).
I have found that my problem i
On Tuesday 09 September 2008 03:05:59
[EMAIL PROTECTED] wrote:
> > If anybody can explain to a bear of little brain :-)
> >
> > Once-upon-a-time xhost + would allow anybody to write to your display.
> > That is
> > no longer true with ltsp-5
> >
> > I have clients say ws001 with user HeHim logged-
On Thu, Sep 4, 2008 at 7:06 AM, jam <[EMAIL PROTECTED]> wrote:
> Hi
>
> If anybody can explain to a bear of little brain :-)
>
> Once-upon-a-time xhost + would allow anybody to write to your display. That
> is
> no longer true with ltsp-5
>
> I have clients say ws001 with user HeHim logged-on.
>
>
On Friday 05 September 2008 22:18:21
[EMAIL PROTECTED] wrote:
> > If anybody can explain to a bear of little brain :-)
> >
> > Once-upon-a-time xhost + would allow anybody to write to your display.
> > That is no longer true with ltsp-5
> >
> > I have clients say ws001 with user HeHim logged-on.
>
On Thu, Sep 4, 2008 at 6:36 PM, jam <[EMAIL PROTECTED]> wrote:
> Hi
>
> If anybody can explain to a bear of little brain :-)
>
> Once-upon-a-time xhost + would allow anybody to write to your display. That is
> no longer true with ltsp-5
>
> I have clients say ws001 with user HeHim logged-on.
>
> IM
James,
My brain is too rusty to answer your specific question, but when I was
trying to figure out a way to send messages to users, several people
suggested that I try jabber.
I setup ejabberd (one of many available choices) on my server, and
configured my users to use pidgin, and now I can se
Hi
If anybody can explain to a bear of little brain :-)
Once-upon-a-time xhost + would allow anybody to write to your display. That is
no longer true with ltsp-5
I have clients say ws001 with user HeHim logged-on.
IMe want to send HeHim a message with xmessage. How can I do that, in
particula
François Patte wrote:
> 1- I have a VIA/S3G Unichrom graphic card. When I use the via driver,
> this one seems to be buggy: although dpms is enabled (read from
> xorg.log), it does not work. I cannot use glx: if I do, desktop of a
> user seems duplicated (icons, images...) So I have to use the
Bonjour,
After some troubles, I have a ltsp TC now working with sound, local
devices and scanner working.
The display is not very fine though: moving a window is not very much
refreshed and you get for sometimes a lot of windows on the screen
before getting only one!
1- I have a VIA/S3G Unich
I seem to have exceeded the limit of X sockets.
On my LTSP server users connect to their desktops using a local VNC server session. The sockets files are found in /tmp/.X11-unix/. On my server they start at X0 and go all the way up to X99. When someone logs in they get a free socket and a co
Continuing my thread ;-)
Think I got it working now.
Reverted back to the original ltsp xkb setup.
added XkbRule in build_x4_cfg
Section "InputDevice"
Identifier "Keyboard0"
Driver "keyboard"
Option "XkbRules" "${XKBRULES:-"xfree86"}"
Option "XkbL
Just discovered that while can now change keyboard setup in kde can no
longer change sessions
with ctl-alt-f2 .
Verified that if I revert to the old xkb directory then ctl-alt-f2 works.
My guess its because sarge uses xfree86 and ltsp uses xorg.
Any ideas?
John
John McMonagle wrote:
>Works
Works for me after I renamed the xkb directory and copied in the files
from my debian sarge install.
Have no clue how one one would change ltsp to fix this :-(
In the simple case that ltsp is on the application server suppose one
could copy the application servers xkb files.
In my larger offices
Krishna-
If you need the thin client to be aware of additional fonts, you need to
do one of two things:
1. Run a font server and tell the thin client to use it
2. *copy* (not symlink) the fonts into the LTSP tree and refresh the
font cache info
#1 is usually both easier to implement and mainta
Hmm-
I got impatient and tried making a symlink by:
cd /opt/ltsp/i386/usr/X11R6/lib/X11/
mv fonts/ fonts.bak/
ln -s /usr/share/fonts/
I restarted the X server (ctrl-Alt-Bksp) and then the workstation
hardware, got a new login and was connected. But the problem persists.
-Krishna
On Wed, 21 Jun
All-
I'm having trouble with Emacs21 finding its' fonts, which causes the error
message (for instance) "Warning: Cannot convert string
"-*-helvetica-medium-r-*--*-120-*-*-*-*-iso8859-1" to type FontStruct" and
makes the stuff I'm editing into empty rectangles. The stuff I've found
researching
Rasmus Ory Nielsen wrote:
> This is really great news!
> Thanks for investigating this.
Glad it helped, although this is not a complete solution.
This needs to be integrated into LTSP somehow, which is not trivial.
But I'm sure Jim will figure something out :)
--
Leonid
_
Hi Leonid,
This is really great news!
Thanks for investigating this.
Thanks,
Rasmus Ory Nielsen
ons, 07 06 2006 kl. 03:34 -0400, skrev Leonid Dubinsky:
> Ondrej Valousek wrote:
>
> > My LTSP4.2 works fine against FC5
>
> Ondrej, thank you for your reply - I was starting to worry. I tried the
Jim McQuillan wrote:
> WOW, that's some great info.
Thank you for your kind words :)
Thank you guys for the great product!
> I'm going to add your message to the wiki, so that others can easily find it.
Cool!
> Then, I'll see if I can figure out how to integrate the changes into
> LTSP, so tha
Hi Leonid,
The answer to your question is simple:
I was wrong, I actually never tried xkb switching against FC5. I am
using it against RHEL 4.2.
But thanks a lot for your explanation - it will be handy some time :-)
Thanks,
Ondrej
Leonid Dubinsky wrote:
> Ondrej Valousek wrote:
>
>
>> My LTSP
Leonid,
WOW, that's some great info.
I'm going to add your message to the wiki, so that others can easily find
it. Then, I'll see if I can figure out how to integrate the changes into
LTSP, so that this problem doesn't happen.
Thanks,
Jim McQuillan
[EMAIL PROTECTED]
On Wed, June 7, 2006 3:34
Ondrej Valousek wrote:
> My LTSP4.2 works fine against FC5
Ondrej, thank you for your reply - I was starting to worry. I tried the
change you suggested, but it did not work. Motivated by the fact that
keyboard switcher works for you, I decided to investigate further. See
[SOLUTION] below.
First
Hi Leonid,
My LTSP4.2 works fine against FC5 - just try to include this
into /etc/build_x4_cfg:
Section "InputDevice"
Identifier "Keyboard0"
Driver "keyboard"
Option "XkbRules" "${XKBRULES:-"xorg"}"
Option "XkbModel" "${XKBMODEL:-"pc105"}"
Optio
I apologize for starting a new thread on this one,
but maybe bolder subject will get noticed :)
I was using Gnome keyboard switcher applet on LTSP 4.1
with a Fedora Core 4 server - no problems. After upgrade
to Fedora Core 5, any layout added to the switcher causes
X server crash on the client. Re
Hi,
This is a request for a memory jogger:
I have been running LTSP thin client on Ubuntu but can't remember how to
stop the server having an X display. With SuSE and ltspconfig
recognising xdmcp it was easy but although I've looked at xdm/gdm
configs I can;t recal what I have to do.
Thanks in a
Catherine,
It sounds like your Xserver is crashing, probably due to running out of
ram. You should try turning on NFS_SWAP, to see if that helps. I'm
guessing that the problem will go away when you do that.
These are the settings to add to the lts.conf file:
USE_NFS_SWAP = Y
SWAPFILE_S
Hi Catherine,
On Thu, 17 Nov 2005, Catherine Stéfan wrote:
I have an LTSP installed on a MEPIS (2.8 Ghz and 1Go of RAM) and one of my
three thin clients (P133, 31Mo RAM) seems to disconnect after a while,
roughly every 10 minutes, whatever I do.
We've seen that problem before as well. We use
Hello,
I have an LTSP installed on a MEPIS (2.8 Ghz and 1Go of RAM) and one of my
three thin clients (P133, 31Mo RAM) seems to disconnect after a while,
roughly every 10 minutes, whatever I do.
Being logged in or not (with KDM still displayed), using the machine or not,
the client seems to res
Kevin Verheyen wrote:
Hello to you all,
Yet all is working fine at our new install base in school,
but i do have a big problem with ooo.
All my pupils use classlogins, ie multiple logins per class
(3 computers using ex. klas6b/klas6b as login pas)
Everytghing works fine, except ooo.
When one t
Hello to you all,
Yet all is working fine at our new install base in school,
but i do have a big problem with ooo.
All my pupils use classlogins, ie multiple logins per class
(3 computers using ex. klas6b/klas6b as login pas)
Everytghing works fine, except ooo.
When one thin client opens OOO, n
On Saturday 20 of August 2005 21:43, Piotr Sobolewski wrote:
> Hi,
>
> I just install an X terminal at my home. The server is Debian, 1 GHz, 256
> MB RAM. The terminal is 60 MHz, 32 MB RAM. After installation I had
> problems with making X server (on terminal) work (you know, normal problems
> with
On Saturday 20 of August 2005 22:01, Jim McQuillan wrote:
> > (...)
> > My problem is that X terminal works so slowly (opening a simple menu
> > lasts up to one second, etc) that it is hard and not nice
> > experience to work on it. I tried to find the bottleneck, and
> > I found it is X server
Piotr,
It's not clear from your message if you are using LTSP.
Also, what is the CPU? You mentioned 60Mhz, so I'm going to guess that
it is a Pentium, but it's not clear.
if you are using LTSP, why can't you run 'startx'?
What kind of video card do you have?
Usually, when people report that i
Hi,
I just install an X terminal at my home. The server is Debian, 1 GHz, 256 MB
RAM. The terminal is 60 MHz, 32 MB RAM. After installation I had problems
with making X server (on terminal) work (you know, normal problems with
configuring X...), so now I start X just using:
/usr/X11R6/bin/Xorg
Strange, I have never had such a problem (LTSP 4.1 & RHEL 3.0 & GDM).
But I know for sure the pinging interval could be setup in gdm.conf
Jim McQuillan wrote:
Joe,
Hoary uses GDM.
GDM has a problem, because it tries to ping the Xserver every 15
seconds. IT's not an ICMP ping. It sends an X r
I will attempt to reboot and then I will refrain from running that
benchmark. If that fixes the problem we won't hear another word about
it (though I may be unable to do any benchmarking, sorry).
Jim McQuillan wrote:
Joe,
Hoary uses GDM.
GDM has a problem, because it tries to ping the X
Jim McQuillan wrote:
Joe,
Hoary uses GDM.
GDM has a problem, because it tries to ping the Xserver every 15
seconds. IT's not an ICMP ping. It sends an X request to the Xserver,
and expects a reply. I think if it doesn't get 3 replies in a row, it
assumes the session is dead, and it kills the
Joe,
Hoary uses GDM.
GDM has a problem, because it tries to ping the Xserver every 15
seconds. IT's not an ICMP ping. It sends an X request to the Xserver,
and expects a reply. I think if it doesn't get 3 replies in a row, it
assumes the session is dead, and it kills the session.
Several of th
Haivng an odd problem on hoary with X involving ltsp. I think my x
sessions are just dying.
I logged in a user on a remote station and set the system to run that
benchmark, figuring I'd come back in an hour or so and see how it was.
I get no graphical interface. it's just gone. Blackscreen
Hi
> I am new to LTSP and just installed it over SuSE 9.2. Installation
> proceeded okay, but now I find that X doesn't start up automatically on my
> server anymore, even though I'm on run level 5.
>
> X does start whenever I run 'startx'.
>
> Before I tinker with the startup scripts, etc.,
Look here:
http://marc.theaimsgroup.com/?l=ltsp-discuss&m=100030060430611&w=2
c
Dominique Cimafranca wrote:
Hello,
I am new to LTSP and just installed it over SuSE 9.2. Installation
proceeded okay, but now I find that X doesn't start up automatically on my
server anymore, even though I'm on run le
Hello,
I am new to LTSP and just installed it over SuSE 9.2. Installation
proceeded okay, but now I find that X doesn't start up automatically on my
server anymore, even though I'm on run level 5.
X does start whenever I run 'startx'.
Before I tinker with the startup scripts, etc., can anyone
Op woensdag 9 maart 2005 09:46, schreef Tribhuwan:
> which config file should we change and which entries are 2 b changed.
/etc/hosts? It's mentioned on the wiki
http://wiki.ltsp.org/twiki/bin/view/Ltsp/Troubleshooting-GrayScreen but only
at the bottom of the page... I think that it would be b
Tribhuwan,
Take a look at this document on our wiki:
http://wiki.ltsp.org/twiki/bin/view/Ltsp/Troubleshooting-GrayScreen
That should help you understand the problem, and fix it.
Jim McQuillan
[EMAIL PROTECTED]
On Wed, 9 Mar 2005, Tribhuwan wrote:
> We r trying 2 configure LTSP 3.1 on our
We r trying 2 configure LTSP 3.1 on our linux server having following
specifications:
Pentium 4 - 1.8 Ghz
256 MB RDRAM
3COM's 3C905C-TX-M for connecting thin client
Intel's 82801DB PRC for reaching LAN and Internet.
OS is Linux Fedora Core 3.
Thin Client specs:
STPC Processor 50 MHz
64Mbits SRAM
I have set ltsp, but this time X does not want to cooperate. Hopefully
someone has a hint were I should look to get it up and running.
The error message is:
scanning for videocard
Building the /tmp/XF86Config-4 file
Cannot open log file /var/log/Xorg.0.0.log
I can provide the following informa
Dears,I have Slackware 10 & LTSP.I have installed Perl
modules on my system.ltspcfg is working,But option of
7 doesn´t work.(configuring XDMCP)
Please guide me that i can configure XDMCP by hand.
Now,My X can up,But it stay,it doesn´t progress.
Even mouse doesn´t convert from a big X to cursor.
Ple
Friends,
I am using ltsp 4.1 and mandrake 10.
Clients with pci lan card (means etherboot) work fine
as expected.
But clients with onboard lan (means with pxe boot)
have problem restarting X after first log out whether
its startx or rdesktop screen.
Any suggestion would be highly appreciated.
Mor
Tirsdag den 7. december 2004 08:45 skrev Verner KjÃrsgaard:
> Mandag den 6. december 2004 16:25 skrev Jim McQuillan:
> > Verner,
> >
> > How much memory do you hve in your thin clients?
> >
> > If it's less than 32mb, you should consider turning on NFS Swap.
> >
> > Jim McQuillan
> > [EMAIL PROTECT
Mandag den 6. december 2004 16:25 skrev Jim McQuillan:
> Verner,
>
> How much memory do you hve in your thin clients?
>
> If it's less than 32mb, you should consider turning on NFS Swap.
>
> Jim McQuillan
> [EMAIL PROTECTED]
>
> On Mon, 6 Dec 2004, Verner [iso-8859-1] KjÃrsgaard wrote:
> > Hi List,
Op maandag 6 december 2004 16:25, schreef Jim McQuillan:
Hi,
How is the colordepth.. KDM and KDE likes more than 256 and old machines in
the LTSP standard gives mostly high resolution but poor colordepth. I had the
same behavior on suse 9.1
Philip
> Verner,
>
> How much memory do you hve in y
Verner,
How much memory do you hve in your thin clients?
If it's less than 32mb, you should consider turning on NFS Swap.
Jim McQuillan
[EMAIL PROTECTED]
On Mon, 6 Dec 2004, Verner [iso-8859-1] Kjærsgaard wrote:
> Hi List,
>
> - I've got nearly all working now, NIC/Floppy boot and all.
>
> T
Hi List,
- I've got nearly all working now, NIC/Floppy boot and all.
The ltsp system is running on SuSE9.2 - and works perfectly well for a number
of clients.
On some old TULIP machines, however, I get the XDM (changed from KDM just for
trying) login - and no more. When I try a login, the cli
Jim McQuillan wrote:
On Sat, 30 Oct 2004, Lanman wrote:
Jim - Just double-checked and you're absolutely right. X is not running when
the terminals are shut off. I ended up editing two copies of the Xservers file
to make it permanent but it's all good now.
#1 - /etc/kde/kdm/Xservers,
#2 - /etc/X11/x
On Sat, 30 Oct 2004, Lanman wrote:
>
> Jim - Just double-checked and you're absolutely right. X is not running when
> the terminals are shut off. I ended up editing two copies of the Xservers file
> to make it permanent but it's all good now.
>
> #1 - /etc/kde/kdm/Xservers,
> #2 - /etc/X11/xdm/Xse
Lanman,
As you have noted the clients depend on the server running XFS (the
font server) and KDM (the display manager) but that does not mean you
need to have KDM manage the display of the server (your CPU problem).
1) Start XFS as you have been. No changes needed.
2) KDM is a display m
Jim McQuillan wrote:
On Sat, 30 Oct 2004, Lanman wrote:
Thanks Jim! That's the one piece of the puzzle that was missing. Server
console is off and terminal booted without a hitch! "Top" is humming along
quite nicely with 'X' and 'xfs' consuming almost nothing for memory and CPU
cycles.
X shouldn'
On Sat, 30 Oct 2004, Lanman wrote:
> Thanks Jim! That's the one piece of the puzzle that was missing. Server
> console is off and terminal booted without a hitch! "Top" is humming along
> quite nicely with 'X' and 'xfs' consuming almost nothing for memory and CPU
> cycles.
X shouldn't be consum
Thanks Jim! That's the one piece of the puzzle that was missing. Server
console is off and terminal booted without a hitch! "Top" is humming
along quite nicely with 'X' and 'xfs' consuming almost nothing for
memory and CPU cycles.
Don't know how I missed that in the documentation, but thanks fo
Lanman,
First of all, you DO need XFS and KDM running on the server.
BUT, you don't need a graphical session on the server.
Look in your kdmrc file (You'll have to find that yourself), and in that
file, there should be a line that says 'Xservers'. That line points to
a file. Something like: /u
Still no luck with X folks. I've tried everything I can think of, but
it's just not making any sense. The only way to get a desktop on a
terminal is to start XFS and KDM on the server at which point the
terminals get a login box right away.
Otherwise I either get the infamous gray screen (haven
Eugene Coetzee wrote:
Lanman wrote:
I forgot to mention that after a reboot, X is running, but not
consuming any noticeable CPU cycles and 0.9% of memory. Once I re-boot
the client that goes up to expected normal levels, but only runs the
CPU up to 99% when the terminal is logged in and sitting
Lanman wrote:
I forgot to mention that after a reboot, X is running, but not
consuming any noticeable CPU cycles and 0.9% of memory. Once I re-boot
the client that goes up to expected normal levels, but only runs the
CPU up to 99% when the terminal is logged in and sitting idle.
This is extra-o
On Fri, 29 Oct 2004, Lanman wrote:
> I forgot to mention that after a reboot, X is running, but not consuming any
> noticeable CPU cycles and 0.9% of memory. Once I re-boot the client that goes
> up to expected normal levels, but only runs the CPU up to 99% when the
> terminal is logged in and s
Lanman,
the 'X' that is consuming cpu is the Xserver running on the Server, NOT
the Xserver that is running on the workstation.
Is a screensaver running?
If so, change it to the blank screen. No flying toasters or spinning
gears or anything like that.
Jim McQuillan
[EMAIL PROTECTED]
On Fri,
I forgot to mention that after a reboot, X is running, but not consuming
any noticeable CPU cycles and 0.9% of memory. Once I re-boot the client
that goes up to expected normal levels, but only runs the CPU up to 99%
when the terminal is logged in and sitting idle.
In order to keep things as si
Back again with another weird one;
I'm working with Mandrake 10.1 and LTSP 4.1. I've set up a test
environment using only one thin-terminal at a time. With that single
terminal logged into the server in graphic mode, I'm seeing the CPU
hitting 99% usage for 'X' when I use 'top' to check the serv
Sudev Barar wrote:
On Wed, 2004-10-27 at 16:26, Lanman wrote:
I just noticed that 'X' is going crazy on my server. It seems to have
been using the swap partition like it was going out of style, because
the hard drive was working overtime as well.
In fact, I was unable to log into the server via
On Wed, 2004-10-27 at 16:26, Lanman wrote:
> I just noticed that 'X' is going crazy on my server. It seems to have
> been using the swap partition like it was going out of style, because
> the hard drive was working overtime as well.
>
> In fact, I was unable to log into the server via ssh for a
I just noticed that 'X' is going crazy on my server. It seems to have
been using the swap partition like it was going out of style, because
the hard drive was working overtime as well.
In fact, I was unable to log into the server via ssh for almost an hour
because it was too overloaded, and as
[This is a repost as the first one hasn't appeared for me. Perhaps a DoS
protection? Sorry for the inconvenience if that wasn't the problem.]
> Give me a solution as soon as possible.
A quick but not optimal solution is to try the "vesa" driver instead (XSERVER
= "vesa"), and see how well (or ra
> Give me a solution as soon as possible.
A quick but not optimal solution is to try the "vesa" driver instead (XSERVER
= "vesa"), and see how well (or rather, how bad) it performs.
/etc/vidlist is only useful if you specify "auto" as XSERVER, so until you get
it working don't care about that,
Hai All,
I have some problem with a LTSP thin client. The problem is the the X-term
is not working and having some error message while I start the X-term in
client machine
Fatal Error
The client Display chipset is Intel 82845GE Mercury Mother Board
LTSP Kernel vmlinuz-2.4.19-ltsp-1
I ha
We're running LTSP 4.1...
The clients immediately boot into a Citrix session with this line in .xinitrc:
/usr/lib/ICAClient/wfcmgr
The user is then able to login to the Citrix Metaframe as normal. The
only problem is that about 1 minute later, X restarts and they're
kicked out. They can log bac
I have a lot of interest in getting some form of compression working with LTSP.
I have been following the messages posted to this list about it. I would like to know if there is anyone that is officially working on this and if there is a collaboration page setup where information can be poste
Where do you set timeout for X being used by terminals?
---
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shippi
On Tuesday 15 June 2004 08:24, Dag Sverre Seljebotn wrote:
> The solution was to turn on swap over the network, and the problem
> completely disappeared. I suggest you just try that and see if that fixes
> the problem. (To reproduce, watch some big pictures in a browser).
Thanks Dag, I'll give th
> We have LTSP deployed in about 30 different locations, deployment was
> completed about 6 weeks ago. Since deployment we've been getting
> complaints that users "get logged out". I believe that what is happening
> is that the X server is getting crashing/resetting.
Only working from brief expe
Hi,
We have LTSP deployed in about 30 different locations, deployment was
completed about 6 weeks ago. Since deployment we've been getting complaints
that users "get logged out". I believe that what is happening is that the X
server is getting crashing/resetting.
Our configuration is LTSP4 b
Tony,
The XF86Config file gets generated automatically for you, based on
entries in the lts.conf file. In most cases, all you need is
to have:
XSERVER = auto
in the [Default] section.
If you want to specify a particular Xserver for a workstation, create
a section for that workstation.
Hello Tony,
Wednesday, April 21, 2004, 11:12:49 PM, you wrote:
> Hello,
> I am setting up a suse 9.0 PC for ltsp, for about 10 current W98 Pcs.
> Done the install and configure and the boot disks (one for each NIC) and dhcp etc.
> Now it all works in text mode.
> There is a mix of video cards, 4
1 - 100 of 297 matches
Mail list logo
