On Tue, Sep 27, 2011 at 11:36:30PM +0530, Ritesh Raj Sarraf wrote:
> Hello, Thank you for packaging ulatencyd. This tool really does what it
> claims. 


Hi,

I'm glad you find this package useful :)

> There are, I believe,  a couple of issues curently.

It would have been better to file a bug for each of the issues you found, 
so that progress for each of them could have been more easily tracked.

Anyways:

> 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.

It sound like the correct behaviour to me. AFAIK if the target directory is 
already mounted there's no way to gracefully handle the error (and yes,
ulatencyd mounts the cgroups). Just to make sure I'll contact the upstream 
author to hear what he thinks.

> 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.

I'm aware of this. The cause is that ulatencyd is started before dbus,
even if its init script lists dbus under Required-Start. I don't know
why it doesn't work though and it doesn't seem to cause any problem (any
that I am aware of).

I'll try a bit more in the next few days but I can't promise anything.

> 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.

This is easily fixable, I think. I'll get the fix uploaded in the next 
version.

> 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.

In the meantime, could you please file a different bug for each of the 
issues?

Thanks for reporting.

Cheers

-- 
perl -E'$_=q;$/= @{[@_]};and s;\S+;<inidehG ordnasselA>;eg;say~~reverse'



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to