Your message dated Sat, 1 Oct 2011 14:45:53 +0200 with message-id <[email protected]> and subject line Re: Bug#643573: various issues with ulatencyd has caused the Debian Bug report #643573, regarding various issues with ulatencyd to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 643573: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643573 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: ulatencyd Version: 0.5.0-3 Severity: normal Hello, Thank you for packaging ulatencyd. This tool really does what it claims. There are, I believe, a couple of issues curently. Issue 1: ERROR: can't mount: /sys/fs/cgroup/cpu aborting... If cgroup is already mounted (in fstab), ulatencyd fails with the above message. Looks like on startup, it tries to mount cgroup. 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 (with issue 1 resolved by disabling cgroup in fstab), ulatencyd starts up successfully with the exception of the consolekit error. Issue 3: ERROR: daemon already running, can't request: org.quamquam.ulatencyd aborting... On restart of ulatencyd daemon, it dies. Looks like it tries to quickly restart and finds the daemon running but triggers the abort code when it cant acquire a request to its service. Subsequent stop/start fixes the problem. Final result 4: Message: CK: Session added /org/freedesktop/ConsoleKit/Session1 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 Message: CK: Session removed /org/freedesktop/ConsoleKit/Session1 Message: CK: Session added /org/freedesktop/ConsoleKit/Session2 Message: CK: Session removed /org/freedesktop/ConsoleKit/Session2 Message: CK: Session added /org/freedesktop/ConsoleKit/Session3 xwatch-Message: connected to X11 host: champaran display: 0 screen: 0 Finally, after working around all the 3 issues, everything works fine. Ritesh -- 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 ---
--- Begin Message ---I'm closing this since single bug reports have been filed for each issue. Cheers -- perl -E'$_=q;$/= @{[@_]};and s;\S+;<inidehG ordnasselA>;eg;say~~reverse'
--- End Message ---
