New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

qvm-sync-clock: do not display nonsense output #607

Closed
marmarek opened this Issue Mar 8, 2015 · 2 comments

Comments

Projects
None yet
2 participants
@marmarek
Member

marmarek commented Mar 8, 2015

Reported by joanna on 26 Jun 2012 08:56 UTC

[~](joanna@dom0)$ qvm-sync-clock 
 ...killed.
 ...killed.
 ...killed.
Tue Jun 26 08:52:44 UTC 2012

Migrated-From: https://wiki.qubes-os.org/ticket/607

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Comment by marmarek on 26 Jun 2012 10:06 UTC
This applies to all qvm-run -p calls.
Seems to be caused by pam_systemd.so: http://lists.freedesktop.org/archives/systemd-devel/2012-March/004771.html. Sadly this fix wasn't released in any bugfix release (the next version is major release). As I don't want to fork systemd package and maintain its support, will try to workaround it by disabling pam_systemd - currently testing if it doesn't introduce any problems.

Member

marmarek commented Mar 8, 2015

Comment by marmarek on 26 Jun 2012 10:06 UTC
This applies to all qvm-run -p calls.
Seems to be caused by pam_systemd.so: http://lists.freedesktop.org/archives/systemd-devel/2012-March/004771.html. Sadly this fix wasn't released in any bugfix release (the next version is major release). As I don't want to fork systemd package and maintain its support, will try to workaround it by disabling pam_systemd - currently testing if it doesn't introduce any problems.

@marmarek marmarek added this to the Release 1 milestone Mar 8, 2015

@marmarek marmarek assigned marmarek and unassigned rootkovska Mar 8, 2015

@marmarek

This comment has been minimized.

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