Losinggeneration/fixes #2

Merged
2 commits merged into from Jan 14, 2011

Conversation

Projects
None yet
2 participants
@losinggeneration
Contributor

losinggeneration commented Jan 14, 2011

I have two commits here that: A) Fix the INSTALL_PREFIX and B) make core.lua installable if DEVELOP_MODE is disabled.

core.lua on this pull request installs to INSTALL_PREFIX/lib/ulatency/core.lua Feel free to skip this commit if you like and change it to something else.

losinggeneration added some commits Jan 14, 2011

Fix INSTALL_PREFIX
* CMAKE_INSTALL_PREFIX is a variable. It wasn't being called as one
  though.
Have core.lua installed by default
* lib/ulatency may not be the best place for it. Perhaps libexec, even
  though it seems that only gcc really uses that...
@poelzi

This comment has been minimized.

Show comment Hide comment
@poelzi

poelzi Jan 14, 2011

Owner

thanks. fixed

Owner

poelzi commented Jan 14, 2011

thanks. fixed

gajdusek referenced this pull request in Szpadel/ulatencyd Feb 24, 2013

gajdusek added a commit that referenced this pull request Mar 19, 2013

Support daemon.media label (e.g. mpd service), issue #2
+ Tag mpd with media.label (simple.d/audio.conf)
+ Update scheduler rules to move non user processes labelled
with daemon.media to sys_media cgroup. They are scheduled similar
to user.media.

gajdusek added a commit that referenced this pull request Mar 21, 2014

Initial support for XDG cookie based sessions that will someday repla…
…ce the old EUID based approach (issue #2)

- new rules/xdg_sessions.lua:
  + Determine if the process is member of a XDG session and set xdg_session flag
- modify scheduler mappings:
  + Use xdg_session label to find out if the process is being run by user.
  + Processes are still moved to cgroups according their EUID.

BUGS: in one-seat-desktop mapping, processes of same XDG session
but with different EUID will be labeled as user.idle, as the code
still determines active sessions by EUID. This will require bigger changes
in the session handling in C core.

This issue was closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment