--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: ulatencyd: start-up timing issue
- From: Ritesh Raj Sarraf <rrs@debian.org>
- Date: Wed, 28 Sep 2011 01:24:45 +0530
- Message-id: <20110927195445.20110.13053.reportbug@champaran.hq.netapp.com>
Package: ulatencyd
Version: 0.5.0-3
Severity: normal
Issue 2:
WARNING: CK Error: Could not get owner of name
'org.freedesktop.ConsoleKit': no such name
simplerules-Message: load simple rules directory:
/etc/ulatencyd/simple.d
xwatch-Message: x server observation active. poll interval: 500
Message: load rule directory: /etc/ulatencyd/rules
Message: load rule directory: /etc/ulatencyd/scheduler
Message: ulatencyd started successfull
On start-up of the OS, ulatencyd starts up successfully with the exception of the
consolekit error.
Probably an initscripts bug. I have parallelism enabled, maybe that's
the cause.
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'testing'), (101, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages ulatencyd depends on:
ii dbus 1.4.16-1
ii libc6 2.13-21
ii libdbus-1-3 1.4.16-1
ii libdbus-glib-1-2 0.96-1
ii libglib2.0-0 2.28.6-3
ii liblua5.1-0 5.1.4-10
ii liblua5.1-posix1 5.1.9-2
ii libpolkit-gobject-1-0 0.102-1
ii libxau6 1:1.0.6-3
ii libxcb1 1.7-3
ii lua5.1 5.1.4-10
ulatencyd recommends no packages.
ulatencyd suggests no packages.
-- Configuration Files:
/etc/ulatencyd/cgroups.conf changed:
-- this is a lua file
CGROUP_ROOT = "/sys/fs/cgroup"
-- /sys/fs/cgroup is not available on older kernels, we need to change that
-- in those cases
fp = io.open(CGROUP_ROOT, "r")
if not fp then
CGROUP_ROOT = "/dev/cgroup"
else
fp:close()
end
-- edit the below only when you know what you are doing
-- describes which subsystems are mounted under
-- which toplevel path
CGROUP_MOUNTPOINTS = {
cpu={"cpu"},
-- please have a look at README.Debian to see why the memory resource
-- controller was disabled, and how to re-enable it.
memory={"memory"},
blkio={"blkio"},
cpuset={"cpuset"}
}
-- FIXME we need some better solution for that :-/
-- cpuset, very powerfull, but can't create a group with unset cpus or mems
CGROUP_DEFAULT = {
cpu={["notify_on_release"] = "1",},
memory={["notify_on_release"] = "1",},
io={["notify_on_release"] = "1",},
cpuset={["notify_on_release"] = "1",},
}
-- no debconf information
--- End Message ---