> niplas did an upgrade and had a wrong /etc/nbd-
server/conf.d/ltsp_i386.conf from his older setup
Just to clarify:
I've tampered with some parts of the ltsp-setup but never touched the
nbd-servers configuration up until now.
This might give a hint towards the problem...
My quickfi
Previous LTSP specific NBD conf differs from new generic default
generated (?) on new build..
New:
[generic]
user = nbd
group = nbd
includedir = /etc/nbd-server/conf.d
Old:
[generic]
user = nobody
group = nogroup
oldstyle = false
Same problem here, appears to happen when: ltsp-build-client...
I do actually have the complete ltsp-build-client output, unfortunatelly it's
in Swedish.
I can paste it somewhere if you like.
As a sidenote, when executed the second time no message about restarting
NBD-server shows up (!)
Instead
=gnome-fallback"
LDM_LIMIT_ONE_SESSION=True
LDM_THEME=ltsp
# FAT_RAM_THRESHOLD=500 "this setting made 512MB clients go thin" reverting
to default (300(?))
# LANG=sv_SE.UTF-8
# LANGUAGE=sv_SE.UTF-8
<*eof*>
/niplas
--
You received this bug notification because you are a member
=gnome-fallback"
LDM_LIMIT_ONE_SESSION=True
LDM_THEME=ltsp
# FAT_RAM_THRESHOLD=500 "this setting made 512MB clients go thin" reverting
to default (300(?))
# LANG=sv_SE.UTF-8
# LANGUAGE=sv_SE.UTF-8
<*eof*>
/niplas
** Package changed: ubuntu => l
e
+ LDM_LANGUAGE=sv_SE.UTF-8
+ SSH_FOLLOW_SYMLINKS=False
+ LDM_SESSION="gnome-session --session=gnome-fallback"
+ LDM_LIMIT_ONE_SESSION=True
+ LDM_THEME=ltsp
# FAT_RAM_THRESHOLD=500 "this setting made 512MB clients go thin" reverting
to default (300(?))
# LANG=sv_SE.UTF-8
#
INKS=False
LDM_SESSION="gnome-session --session=gnome-fallback"
LDM_LIMIT_ONE_SESSION=True
LDM_THEME=ltsp
# FAT_RAM_THRESHOLD=500 "this setting made 512MB clients go thin" reverting to
default (300(?))
# LANG=sv_SE.UTF-8
# LANGUAGE=sv_SE.UTF-8
<*eof*>
/niplas
** Affect
Whoops
No I cant verify all of the above :D but I sometimes do slip on ctrl-V
Also: In an LTSP FAT-client environment (generic
3.0.0.14/i386/allbuntu/verified) this should be considered a bug.
On a desktop or server default install it still is a default behaviour not
acting nice at all (despite
I can verify all of the above
This major annoyance (seems a bit harsh to call it a bug though :) is
especially frustrating in an LTSP environment.
Firstly because the hardware even for fat clients usually is quite
modest in terms of performance, and second (which is worst) the process
is absolut
Public bug reported:
Tried using Gnome system monitor 3.2.1 on various older systems.
Results as follows:
near zero utilization in 'system' and 'filesystem'
utilization as follows in 'processes' and 'resources', somewhat lower
utilization for processes.
Dual Xeon HT (Quad virtual cores) netburst
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/918558
Title:
Unreasonable CPU-usage in monitoring
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-system-
://help.ubuntu.com/11.10/index.html and
https://help.ubuntu.com/11.04/index.html respectively
/Niplas
** Affects: ubuntu-docs (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
12 matches
Mail list logo
