sysctl dev.rtc.max-user-freq no longer exists in the kernel
by Chuck Anderson
What happened to this sysctl? It appears that some stuff depends on
this setting, e.g. kqemu. There is only a hpet.max-user-freq now and
I get this funky permission error on 'sysctl -a':
# /sbin/sysctl -a | grep freq
error: permission denied on key 'kernel.sched_nr_migrate'
dev.hpet.max-user-freq = 64
# /sbin/sysctl -n -q dev.rtc.max-user-freq
error: "dev.rtc.max-user-freq" is an unknown key
16 years
fiddling with livecd-creator
by subhodip biswas
hi !
i have two questions. though unrelated still i asked them at once :
--------------------
i used livecd-fedora-base-desktop.ks in order to built a live cd
using live cd creator . Now i am little bit worried about the packages
downloaded. Because it already did a 620 MB download. Have i done
anything wrong here.
I just needed a basic GNOME Desktop.
----------------------
One more question . Can Filesystem structure be created within a
directory say /opt as in ltsp . if yes ..how ?
--
Regards
Subhodip Biswas
GPG key : FAEA34AB
Server : pgp.mit.edu
http://subhodipbiswas.wordpress.com
http:/www.fedoraproject.org/wiki/SubhodipBiswas
16 years
KDE-SIG weekly report (10/2008)
by Sebastian Vahl
This is a report of the weekly KDE-SIG-Meeting with a summary of the
topics that were discussed. If you want to add a comment please reply
to this email or add it to the related meeting page.
----------------------------------------------------------------------------------
= Weekly KDE Summary =
Week: 10/2008
Time: 2008-03-04 16:00 UTC
Meeting page: http://fedoraproject.org/wiki/SIGs/KDE/Meetings/2008-03-04
Meeting log:
http://fedoraproject.org/wiki/SIGs/KDE/Meetings/2008-03-04?action=AttachF...
----------------------------------------------------------------------------------
= Participants =
- KevinKofler
- LukasTinkl
- PavelShevchuk (stalwart)
- SebastianVahl
- ThanNgo
----------------------------------------------------------------------------------
= Agenda =
topics to discuss:
- PolicyKit integration (#428212)
- KDE 4.0.2
- Packaging API docs
- Getting KDE 4 to use kde-settings defaults
- Latest live CD testing feedback
- Using ON_DEV when claiming bugs because ASSIGNED is now used for a different
purpose by the triage team
- split out of khelpcenter from kdebase3 (#435133 and #435873)
recent bugs:
#435656: closing bluemarble causes desktop session to end
#435956: yum update removes kdewebdev
= Summary =
o PolicyKit integration:
- LukasTinkl started a discussion with WillStephenson on how to implement
PolicyKit support
- But for the time being no work has done.
- We should consider a quick hack for getting PolicyKit working for the Beta
- Full PolicyKit support seems to be implemented by upstream for KDE 4.1
o KDE 4.0.2:
- KDE 4.0.2 is already in rawhide, official release will be tomorrow.
- The docs in kde-l10n are still broken.
- 4.0.2 versions of kiconedit and kcoloredit were built today.
o Packaging API docs:
- Currently we're not building API docs at all.
- We should package it as *-apidocs sub packages like in KDE 3.
- They should be provided at least for kdelibs, maybe kdepimlibs and soprano.
- For minor packages api.kde.org is the place to start (unless someone files a
bug for including them).
o Getting KDE 4 to use kde-settings defaults:
- KDE4 doesn't use the kiosktool setup we use in kde-settings.
- This is also affecting the "KDE Development Platform" provided for F7 and F8
(eg. dolphin).
- Short term solution: move the global configs back to $KDEDIR/share/config/ .
- Long term solution: fix KDE 4 to recognize the kiosk settings (with/in
upstream).
o Latest live CD testing feedback:
- SebastianVahl prepared an actual live image for internal testing before the
Beta.
- KevinKofler reported some problems when running the image in qemu which
don't seem to appear when running it natively:
- KOrganizer's reminder applet isn't docked to plasma's systray
- nm-applet isn't starting or connecting
- This is maybe related to a not started dbus-session.
- The "next" button in the installer seems to not work sometimes.
- Because gparted was removed from livecd-fedora-base-desktop.ks amarok is
back on the live images.
o Using ON_DEV when claiming bugs because ASSIGNED is now used for a different
purpose by the triage team:
- According to recent changes of the bug triage team we should use ON_DEV
instead of ASSIGNED now.
- Proposed workflow: the person who takes responsibility for that bug assigns
it to himself and set it to ON_DEV.
o Split out of khelpcenter from kdebase3:
- KDE3 applications will work fine with KDE4's khelpcenter but will
need /usr/share/services/khelpcenter.desktop.
- The decision was to include this as a seperate source in kdebase-runtime and
avoid a hard require for khelpcenter.
- So any KDE3 application will need also kdebase-runtime for displaying the
help (which will mainly affect non-KDE users).
- This will also free up some space on the live images because kdebase3 isn't
needed for one single file.
- We should consider adding this to the release notes.
recent bugs:
o Closing bluemarble causes desktop session to end:
- The "3D Earth Desktop" applet kills the X-Server when using it without
enabled OpenGL shaders support.
- This is known upstream but nobody knows how to fix this.
- Also the next release of extragear-plasma is not scheduled before KDE 4.1.
- So bluemarble will be disabled for now.
o yum update removes kdewebdev:
- This is regarding to the multilib obsoletes hack introduced by the split
into *-libs sub packages.
- Because only kdewebdev requires kdewebdev-libs we will add a "Requires:
kdewebdev" to kdewebdev-libs.
----------------------------------------------------------------------------------
= Next Meeting =
http://fedoraproject.org/wiki/SIGs/KDE/Meetings/2008-03-11
----------------------------------------------------------------------------------
= Links =
Buglist:
https://bugzilla.redhat.com/show_bug.cgi?id=428212
https://bugzilla.redhat.com/show_bug.cgi?id=435133
https://bugzilla.redhat.com/show_bug.cgi?id=435656
https://bugzilla.redhat.com/show_bug.cgi?id=435873
https://bugzilla.redhat.com/show_bug.cgi?id=435956
16 years
Retiring idioskopos
by Rick L. Vinyard, Jr.
I don't think it's worth it to orphan this package since I'm upstream,
and this isn't an approach I don't think is viable anymore.
16 years
RFE? Re-detect hardware
by Les Mikesell
Would it be possible to add a feature to rescue mode and/or the livecd
to fix things up after a move to new hardware? That is, check and re-do
all of the stuff that happens during an install to build the initrd
image in /boot, re-install grub, set up X and the other
hardware-related black magic that happens in an install? The obvious
use case would be where your motherboard fries and you move the disk(s)
to another box with a controller that needs a different driver, but you
get the same scenario if you've done a backup/restore or you want to
convert something that has been running under vmware to real hardware.
In the backup/restore case it may also be necessary to fix up /etc/fstab
and/or partition labels to match but I'm not so concerned about the
parts where the changes are known and intentional as I am about having
to know as much as the installer does about matching hardware to drivers.
Does such a thing already exist, and if not, where is the right place to
file an RFE?
--
Les Mikesell
lesmikesell(a)gmail.com
16 years
Conflict between smbios-utils and libsmbios-bin
by Richard W.M. Jones
I'm not quite sure how to get out of this conflict. I've tried
removing and updating individual packages, but to no avail.
Rich.
Setting up Update Process
Resolving Dependencies
--> Running transaction check
---> Package kernel.i686 0:2.6.25-0.82.rc3.git2.fc9 set to be installed
---> Package rsync.i386 0:3.0.0-1.fc9 set to be updated
---> Package NetworkManager-gnome.i386 1:0.7.0-0.8.svn3370.fc9 set to be updated
---> Package xorg-x11-drv-i810.i386 0:2.2.1-3.fc9 set to be updated
---> Package ocaml-pxp.i386 0:1.2.0test1-6.fc9 set to be updated
---> Package dhcpv6-client.i386 0:1.0.13-1.fc9 set to be updated
---> Package firefox.i386 0:3.0-0.beta3.33.nightly20080302.fc9 set to be updated
---> Package mesa-libGL.i386 0:7.1-0.18.fc9 set to be updated
---> Package mesa-libGLU.i386 0:7.1-0.18.fc9 set to be updated
---> Package gnome-desktop.i386 0:2.21.92-3.fc9 set to be updated
---> Package control-center.i386 1:2.21.92-3.fc9 set to be updated
---> Package mesa-libGL-devel.i386 0:7.1-0.18.fc9 set to be updated
---> Package xorg-x11-drv-nv.i386 0:2.1.7-3.fc9 set to be updated
---> Package NetworkManager-glib.i386 1:0.7.0-0.8.svn3370.fc9 set to be updated
---> Package xulrunner.i386 0:1.9-0.beta3.33.nightly20080302.fc9 set to be updated
---> Package hal.i386 0:0.5.10-6.fc9 set to be updated
--> Processing Dependency: smbios-utils for package: hal
---> Package xorg-x11-drv-ati.i386 0:6.8.0-3.fc9 set to be updated
---> Package upstart.i386 0:0.3.9-9.fc9 set to be updated
---> Package mesa-libOSMesa.i386 0:7.1-0.18.fc9 set to be updated
---> Package libdhcp6client.i386 0:1.0.13-1.fc9 set to be updated
---> Package hal-devel.i386 0:0.5.10-6.fc9 set to be updated
---> Package control-center-filesystem.i386 1:2.21.92-3.fc9 set to be updated
---> Package elfutils-libelf-devel.i386 0:0.133-2.fc9 set to be updated
---> Package hal-libs.i386 0:0.5.10-6.fc9 set to be updated
---> Package ocaml-pxp-devel.i386 0:1.2.0test1-6.fc9 set to be updated
---> Package elfutils.i386 0:0.133-2.fc9 set to be updated
---> Package glx-utils.i386 0:7.1-0.18.fc9 set to be updated
---> Package mlocate.i386 0:0.19-1 set to be updated
---> Package elfutils-libs.i386 0:0.133-2.fc9 set to be updated
---> Package elfutils-libelf.i386 0:0.133-2.fc9 set to be updated
---> Package libmtp.i386 0:0.2.6-1.fc9 set to be updated
---> Package gnome-desktop-devel.i386 0:2.21.92-3.fc9 set to be updated
---> Package mesa-libGLU-devel.i386 0:7.1-0.18.fc9 set to be updated
---> Package kernel-devel.i686 0:2.6.25-0.82.rc3.git2.fc9 set to be installed
---> Package NetworkManager.i386 1:0.7.0-0.8.svn3370.fc9 set to be updated
---> Package kernel-headers.i386 0:2.6.25-0.82.rc3.git2.fc9 set to be updated
---> Package gnome-settings-daemon.i386 0:2.21.92-2.fc9 set to be updated
--> Running transaction check
---> Package smbios-utils.i386 0:2.0.1-1.fc9 set to be updated
--> Processing Dependency: libsmbios = 2.0.1-1.fc9 for package: smbios-utils
--> Processing Dependency: libsmbios.so.2 for package: smbios-utils
--> Running transaction check
---> Package libsmbios.i386 0:2.0.1-1.fc9 set to be updated
--> Finished Dependency Resolution
--> Running transaction check
---> Package kernel.i686 0:2.6.25-0.82.rc3.git2.fc9 set to be installed
---> Package rsync.i386 0:3.0.0-1.fc9 set to be updated
---> Package NetworkManager-gnome.i386 1:0.7.0-0.8.svn3370.fc9 set to be updated
---> Package xorg-x11-drv-i810.i386 0:2.2.1-3.fc9 set to be updated
---> Package ocaml-pxp.i386 0:1.2.0test1-6.fc9 set to be updated
---> Package kernel-devel.i686 0:2.6.25-0.80.rc3.git2.fc9 set to be erased
---> Package dhcpv6-client.i386 0:1.0.13-1.fc9 set to be updated
---> Package firefox.i386 0:3.0-0.beta3.33.nightly20080302.fc9 set to be updated
---> Package mesa-libGL.i386 0:7.1-0.18.fc9 set to be updated
---> Package mesa-libGLU.i386 0:7.1-0.18.fc9 set to be updated
---> Package gnome-desktop.i386 0:2.21.92-3.fc9 set to be updated
---> Package control-center.i386 1:2.21.92-3.fc9 set to be updated
---> Package libsmbios.i386 0:2.0.1-1.fc9 set to be updated
---> Package mesa-libGL-devel.i386 0:7.1-0.18.fc9 set to be updated
---> Package xorg-x11-drv-nv.i386 0:2.1.7-3.fc9 set to be updated
---> Package NetworkManager-glib.i386 1:0.7.0-0.8.svn3370.fc9 set to be updated
---> Package xulrunner.i386 0:1.9-0.beta3.33.nightly20080302.fc9 set to be updated
---> Package hal.i386 0:0.5.10-6.fc9 set to be updated
---> Package xorg-x11-drv-ati.i386 0:6.8.0-3.fc9 set to be updated
---> Package upstart.i386 0:0.3.9-9.fc9 set to be updated
---> Package mesa-libOSMesa.i386 0:7.1-0.18.fc9 set to be updated
---> Package libdhcp6client.i386 0:1.0.13-1.fc9 set to be updated
---> Package hal-devel.i386 0:0.5.10-6.fc9 set to be updated
---> Package control-center-filesystem.i386 1:2.21.92-3.fc9 set to be updated
---> Package kernel.i686 0:2.6.25-0.80.rc3.git2.fc9 set to be erased
---> Package elfutils-libelf-devel.i386 0:0.133-2.fc9 set to be updated
---> Package hal-libs.i386 0:0.5.10-6.fc9 set to be updated
---> Package smbios-utils.i386 0:2.0.1-1.fc9 set to be updated
---> Package ocaml-pxp-devel.i386 0:1.2.0test1-6.fc9 set to be updated
---> Package elfutils.i386 0:0.133-2.fc9 set to be updated
---> Package glx-utils.i386 0:7.1-0.18.fc9 set to be updated
---> Package mlocate.i386 0:0.19-1 set to be updated
---> Package elfutils-libs.i386 0:0.133-2.fc9 set to be updated
---> Package elfutils-libelf.i386 0:0.133-2.fc9 set to be updated
---> Package libmtp.i386 0:0.2.6-1.fc9 set to be updated
---> Package gnome-desktop-devel.i386 0:2.21.92-3.fc9 set to be updated
---> Package mesa-libGLU-devel.i386 0:7.1-0.18.fc9 set to be updated
---> Package kernel-devel.i686 0:2.6.25-0.82.rc3.git2.fc9 set to be installed
---> Package NetworkManager.i386 1:0.7.0-0.8.svn3370.fc9 set to be updated
---> Package kernel-headers.i386 0:2.6.25-0.82.rc3.git2.fc9 set to be updated
---> Package gnome-settings-daemon.i386 0:2.21.92-2.fc9 set to be updated
--> Finished Dependency Resolution
Dependencies Resolved
=============================================================================
Package Arch Version Repository Size
=============================================================================
Installing:
kernel i686 2.6.25-0.82.rc3.git2.fc9 development 18 M
kernel-devel i686 2.6.25-0.82.rc3.git2.fc9 development 5.1 M
Updating:
NetworkManager i386 1:0.7.0-0.8.svn3370.fc9 development 683 k
NetworkManager-glib i386 1:0.7.0-0.8.svn3370.fc9 development 70 k
NetworkManager-gnome i386 1:0.7.0-0.8.svn3370.fc9 development 293 k
control-center i386 1:2.21.92-3.fc9 development 2.7 M
control-center-filesystem i386 1:2.21.92-3.fc9 development 35 k
dhcpv6-client i386 1.0.13-1.fc9 development 123 k
elfutils i386 0.133-2.fc9 development 224 k
elfutils-libelf i386 0.133-2.fc9 development 57 k
elfutils-libelf-devel i386 0.133-2.fc9 development 23 k
elfutils-libs i386 0.133-2.fc9 development 177 k
firefox i386 3.0-0.beta3.33.nightly20080302.fc9 development 1.1 M
glx-utils i386 7.1-0.18.fc9 development 38 k
gnome-desktop i386 2.21.92-3.fc9 development 975 k
gnome-desktop-devel i386 2.21.92-3.fc9 development 40 k
gnome-settings-daemon i386 2.21.92-2.fc9 development 422 k
hal i386 0.5.10-6.fc9 development 458 k
hal-devel i386 0.5.10-6.fc9 development 30 k
hal-libs i386 0.5.10-6.fc9 development 61 k
kernel-headers i386 2.6.25-0.82.rc3.git2.fc9 development 687 k
libdhcp6client i386 1.0.13-1.fc9 development 89 k
libmtp i386 0.2.6-1.fc9 development 84 k
mesa-libGL i386 7.1-0.18.fc9 development 11 M
mesa-libGL-devel i386 7.1-0.18.fc9 development 453 k
mesa-libGLU i386 7.1-0.18.fc9 development 210 k
mesa-libGLU-devel i386 7.1-0.18.fc9 development 96 k
mesa-libOSMesa i386 7.1-0.18.fc9 development 2.1 M
mlocate i386 0.19-1 development 55 k
ocaml-pxp i386 1.2.0test1-6.fc9 development 4.0 M
ocaml-pxp-devel i386 1.2.0test1-6.fc9 development 1.5 M
rsync i386 3.0.0-1.fc9 development 275 k
upstart i386 0.3.9-9.fc9 development 240 k
xorg-x11-drv-ati i386 6.8.0-3.fc9 development 392 k
xorg-x11-drv-i810 i386 2.2.1-3.fc9 development 377 k
xorg-x11-drv-nv i386 2.1.7-3.fc9 development 95 k
xulrunner i386 1.9-0.beta3.33.nightly20080302.fc9 development 9.3 M
Removing:
kernel i686 2.6.25-0.80.rc3.git2.fc9 installed 49 M
kernel-devel i686 2.6.25-0.80.rc3.git2.fc9 installed 33 M
Installing for dependencies:
libsmbios i386 2.0.1-1.fc9 development 205 k
smbios-utils i386 2.0.1-1.fc9 development 108 k
Transaction Summary
=============================================================================
Install 4 Package(s)
Update 35 Package(s)
Remove 2 Package(s)
Total size: 61 M
Is this ok [y/N]: y
Downloading Packages:
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test
Transaction Check Error:
file /usr/sbin/assetTag from install of smbios-utils-2.0.1-1.fc9.i386 conflicts with file from package libsmbios-bin-0.13.13-1.fc9.i386
file /usr/sbin/dellBiosUpdate from install of smbios-utils-2.0.1-1.fc9.i386 conflicts with file from package libsmbios-bin-0.13.13-1.fc9.i386
file /usr/sbin/dellLcdBrightness from install of smbios-utils-2.0.1-1.fc9.i386 conflicts with file from package libsmbios-bin-0.13.13-1.fc9.i386
file /usr/sbin/dellWirelessCtl from install of smbios-utils-2.0.1-1.fc9.i386 conflicts with file from package libsmbios-bin-0.13.13-1.fc9.i386
file /usr/sbin/getSystemId from install of smbios-utils-2.0.1-1.fc9.i386 conflicts with file from package libsmbios-bin-0.13.13-1.fc9.i386
file /usr/sbin/propertyTag from install of smbios-utils-2.0.1-1.fc9.i386 conflicts with file from package libsmbios-bin-0.13.13-1.fc9.i386
file /usr/sbin/serviceTag from install of smbios-utils-2.0.1-1.fc9.i386 conflicts with file from package libsmbios-bin-0.13.13-1.fc9.i386
file /usr/sbin/verifySmiPassword from install of smbios-utils-2.0.1-1.fc9.i386 conflicts with file from package libsmbios-bin-0.13.13-1.fc9.i386
file /usr/sbin/wakeupCtl from install of smbios-utils-2.0.1-1.fc9.i386 conflicts with file from package libsmbios-bin-0.13.13-1.fc9.i386
Error Summary
-------------
--
Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones
virt-p2v converts physical machines to virtual machines. Boot with a
live CD or over the network (PXE) and turn machines into Xen guests.
http://et.redhat.com/~rjones/virt-p2v
16 years
[RFC] libcg: design and plans
by Dhaval Giani
Hi,
We have been working on a library for control groups which would provide
simple APIs for programmers to utilize from userspace and make use of
control groups.
We are still designing the library and the APIs. I've attached the
design (as of now) to get some feedback from the community whether we
are heading in the correct direction and what else should be addressed.
We have a project on sourceforge.net at
https://sourceforge.net/projects/libcg and the mailing list (cc'd here)
can be found at https://lists.sourceforge.net/lists/listinfo/libcg-devel
Thanks,
--
libcg
1. Aims/Requirements
2. Design
3. APIs
4. Configuration Scheme
1. Aims/Requirements
1.1 What are Control Groups
Control Groups provide a mechanism for aggregating/partitioning sets of
tasks, and all their future children, into hierarchical groups with
specialized behaviour [1]. It makes use of a filesystem interface.
1.2 Aims of libcg
libcg aims to provide programmers easily usable APIs to use the control
group file system. It should satisfy the following requirements
1.2.1. Provide a programmable interface for cgroups
This should allow applications to create cgroups using something like
create_cgroup() as opposed to having to go the whole filesystem route.
1.2.2. Provide persistent configuration across reboots
Control Groups have a lifetime of only one boot cycle. The configuration
is lost at reboot. Userspace needs to handle this issue. This is handled
by libcg
1.2.3. Provide a programmable interface for manipulating configurations
This should allow libcg to handle changing application requirements. For
example, while gaming, you might want to reduce the cpu power of other
groups whereas othertimes you would want greater CPU power for those
groups.
2. Design
2.1 Architecture
2.1.1 Global overview
libcg will be consumed in the following fashion
---------------------------
| applications |
---------------------------
| libcg |
---------------------------
| kernel |
---------------------------
A more detailed example would be as follows. Consider various applications
running at the same time on a system. A typical system would be running
a web browser, a mail client, a media player and office software. libcg
could be used to group these applications into various groups and give
them various resources. A possible example would be three groups, Internet,
Entertainment and Office. A daemon could attach tasks to these groups according
to some rules and the adminstrator can control the resources attached to each
group via the configuration manager.i
Internet Office Entertainment
---------------------- -------------- -----------
| firefox mutt | | openoffice | | mplayer |
---------------------- -------------- -----------
\ | /
\ | /
------------------------------------------------------
| Some daemon |
------------------------------------------------------
| libcg |
------------------------------------------------------
| kernel |
------------------------------------------------------
2.1.2
libcg will consist of two main parts. The configuration manager and the
library.
The configuration manager will used to maintain the configurations, to load
and unload the configurations, to set the bootup configurations and so on.
This is similar to the network configuration. A configuration file is used
to setup the networking at bootup. Similarly a configuration file will be
used to setup the default control groups (and maybe the top level control
groups) at bootup.
The administrator can directly access the configuration files, and
applications can access it through the library. The configuration manager
is used to provide the persistence.
Application Administrator
| |
V |
library APIs |
\ /
\ /
\ /
V V
libcg configuration files
|
|
V
libcg configuration manager
The configuration manager has to provide isolation between various users of
libcg. That is, if two different users A and B are making use of libcg, then
the configuration manager has to ensure that user A does not affect user B's
settings/configurations.
The top level limits and permissions for A and B are to be provided by the
administrator. The permissions are filesystem permissions as cgroup is
filesystem based.
With this architecure in mind, we expect two levels of configuration files.
One would be the global configuration which the administrator would control
and setup the groups, and a local configuration which the group owner will
control.
A simple example could be that the administrator could split the top level
according to uid, and then each user could control the resources available
to him and group those applications accordingly.
root
|
-------------------------------------------------
| |
A B
|- browsers |- compilers
|- games |- internet
|- office |- dev-environment
|- entertainment |- others
In this example, we have an example cgroup filesystem configuration.
The administrator decides the resources available to "A" and "B". Both "A" and
"B" have followed grouping according to their usage. They decide the resources
availble to their groups (which is dependent of the resources alloted to them
by the adminstrator).
libcg will be written mainly in C with lex and yacc for parsing the configuration
files.
3. APIs
The APIs are envisaged to be of two main types
3.1. Manipulating Control Groups
3.1.1. Create Control Group: This API is proposed to create control groups.
It should take care of the following scenarios
3.1.1.1 Create non persistent control groups: These groups should exist
for just duration of this run. They should not stick across different sessions.
3.1.1.2 Create persistent control groups: These groups should stick across
different sessions.
3.1.2 Delete Control Group: This API is proposed to delete control groups.
It would have the same scenarios as expected for Create Control Group.
3.1.2 Modify Control Group: This API proposed to modify an already
existing group's control files. It too should handle the persistence issue
as like Create Control Group does.
More details about configuration are available in sections 2 and 4.
3.2. Manipulating Configurations
3.2.1. Generate Configuration File: If a cgroup filesystem hierarchy already exists,
it should be possible to generate a configuration file which can create it. This
is proposed to be provided by this API.
3.2.2. Change Configuration File: If one configuration is currently loaded in
memory, it is possible for it to be replaced with the new file. This API proposes
to implement that.
3.2.3. Manipulate Configuration File: This API proposes to allow the configuration
file to be modified.
We should also plan on taking care of statistics once its available in mainline.
4. Configuration Scheme
There are multiple configuration levels. The basic wlm.conf file will provide
the mount points and the controller details. This can only be manipulated by
the adminstrator. No APIs will be provided to modify this file.
There will be group specific configuration files as well. The exact details
of the same still need to be worked out.
4.1. Sample configuration files
4.1.1. Sample wlm.conf
#
# controller file
#
group ca1 {
perm {
task {
uid = balbir;
gid = cgroup;
}
admin {
uid = root;
gid = cgroup;
}
}
cpu {
cpu.shares = 500;
}
}
mount {
cpu = /container;
}
This is an example of a top level group. The mount{} block is used to provide
the mount point of the various controllers. For eg, the cpu controller is
mounted at /container. Next we have the group ca1. This is the top level group
and its permissions are given by the uid and gid fields for tasks and admin. The
next is the individual controller block. For the mount point of cpu, the cpu.shares
value is provided. Thus the above file can be represented as the following script
mkdir /container
mount -t cgroup -o cpu none /container
mkdir /container/ca1
/bin/echo 500 > /container/ca1/cpu.shares
chown -R root /container/ca1
chgrp -R cgroup /container/ca1
chown balbir /container/ca1/tasks
chgrp cgroup /container/ca1/tasks
5. References
1. Documentation/cgroups.txt in kernel sources.
--
regards,
Dhaval
16 years
Re: rawhide report: 20080229 changes
by Adam Jackson
On Fri, 2008-02-29 at 21:12 -0700, Kevin DeKorte wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Rawhide wrote:
>
> On the intel G35 video chip this release is no good...
>
> No display on any output: VGA, DVI, HDMI
> After pulling intel driver from git (master branch) I can get get
> display, but using anything with Mesa crashes X hard
Should be sorted in i810 2.2.1-4.fc9.
- ajax
16 years
rawhide buildroot broken: cannot find kernel-headers!
by Hans de Goede
Hi all,
It seems to be impossible to build packages for rawhide at the moment:
DEBUG util.py:240: run cmd timeout(0): /usr/bin/yum --installroot
/var/lib/mock/dist-f9-build-153127-24988/root/ groupinstall build
DEBUG util.py:261: Error: Missing Dependency: kernel-headers is needed by
package glibc-headers
DEBUG util.py:261: Error: Missing Dependency: kernel-headers >= 2.2.1 is
needed by package glibc-headers
Can someone please fix this (maybe untag the latest kernel build, I don't know
the cause).
Regards,
Hans
16 years