Hi
On Mon, Jan 5, 2015 at 10:07 AM, Oleg Samarin osamari...@gmail.com wrote:
Hello!
The default systemd behavior is to grant/revoke access on devices
attached to a seat when the user activates/deactivates a session on the
seat.
But sometimes it needs the user has an access to some device
Hi Andrei,
07.01.2015 11:51, Andrei Borzenkov:
[...]
I supposed StandardOutput/StandardError=journal+console option is
there exactly for that, but apparently log_error() only writes to the
journal?
openSUSE bug caused by patch set-and-use-default-logconsole.patch.
Yes! You are right! I've
Hi,
07.01.2015 4:50, Chris Murphy:
[...]
These are all really good questions, and it makes me wonder about the
handling when long or failed fsck presents on systems with GUI boot
e.g. plymouth on Fedora. That's a tangent topic from your concern but
seems like there'd need to be a way for systemd
This patch doesn't work as I expected so please skip it - sorry for the
confusion.
On 01/05/2015 05:03 PM, Lukasz Skalski wrote:
To keep compatibility with dbus-1, before we use synthetic_reply_method_*()
functions, we should overwrite 'sender' field - otherwise functions
Signed-off-by: Jonas Ådahl jad...@gmail.com
---
hwdb/70-mouse.hwdb | 3 +++
1 file changed, 3 insertions(+)
diff --git a/hwdb/70-mouse.hwdb b/hwdb/70-mouse.hwdb
index 32a8a5d..38afee0 100644
--- a/hwdb/70-mouse.hwdb
+++ b/hwdb/70-mouse.hwdb
@@ -159,6 +159,9 @@ mouse:usb:v046dpc050:name:Logitech
В Tue, 06 Jan 2015 21:33:15 +0300
Nikolai Zhubr n-a-zh...@yandex.ru пишет:
Hi again,
06.01.2015 19:46, Andrei Borzenkov wrote:
[...]
By executing systemctl status systemd-fsck@... as instructed? Or
journalctl ...
Ok, thanks, I've finally found the messages of my interest by using:
Thanks for the review.
Pushed as b7e7184634d573fb73143210962acce205f37f61
2015-01-06 0:25 GMT+01:00 Zbigniew Jędrzejewski-Szmek zbys...@in.waw.pl:
On Tue, Jan 06, 2015 at 12:01:35AM +0100, Michael Biebl wrote:
Hi,
2015-01-05 14:35 GMT+01:00 Zbigniew Jędrzejewski-Szmek zbys...@in.waw.pl:
On Tue, 06.01.15 10:52, dE (de.tec...@gmail.com) wrote:
Hi.
I dont have a better term.
When you look at the status of a unit or check the output of list-units,
there's a 'load/loaded' column/field also there's an active field/column.
What do these mean? I suspect load/loaded states
Hello all
I'd like to find a clean way to halt a systemd system (actually, a
Docker container) when a main service stops (not just on failure).
I tried Conflicts=systemd-halt.service and calling shutdown from
ExecStopPost= but it seems both cause problems, since I end up with a
stop job for my
Hello Askar,
Askar Safin [2015-01-07 1:13 +0300]:
Hi. It seems you missed my prev. letter. So, I am sending you the patch
again. Typo fix in README in libabc:
-Make your code safe for unexpected termination and any point:
+Make your code safe for unexpected termination at any point:
I (and
В Wed, 07 Jan 2015 23:23:27 -0300
Cristian Rodríguez crrodrig...@opensuse.org пишет:
El 07/01/15 a las 22:55, Nikolai Zhubr escribió:
08.01.2015 4:12, Cristian Rodríguez:
El 07/01/15 a las 21:43, Lennart Poettering escribió:
Maybe suse forgot to include this service file in the initrd or
Hi,
Please disregard. The delay in question was not caused by swap.
Probably I'll come back for advice later when I gather more info.
Still in progress.
Thank you.
Nikolai
07.01.2015 20:59, me wrote:
Hi,
Looking at bootlog console messages, I noticed something strange.
systemd says:
Hi,
I'm not quite sure if it belongs to systemd or rather dracut or even
opensuse bugtracker... Please feel free to redirect me as appropriate.
Below is a fragment of jounal of one boot of opensuse 13.2, irrelevant
parts replaced by dots to compact it a bit.
In short, AFAICS:
1. In initrd,
On Thu, 08.01.15 03:36, Nikolai Zhubr (n-a-zh...@yandex.ru) wrote:
Hi,
I'm not quite sure if it belongs to systemd or rather dracut or even
opensuse bugtracker... Please feel free to redirect me as appropriate.
Below is a fragment of jounal of one boot of opensuse 13.2, irrelevant parts
El 07/01/15 a las 21:43, Lennart Poettering escribió:
Maybe suse forgot to include this service file in the initrd or so?
Correct. It appears to be a bug in the dracut package. I wonder why ..
___
systemd-devel mailing list
On Wed, Jan 7, 2015 at 9:45 PM, Oleg Samarin osamari...@gmail.com wrote:
After adding the simple udev rule:
--
KERNEL==seq, SUBSYSTEM==sound, TAG+=shared
--
/dev/snd/seq becomes accessible
Hi
On Wed, Jan 7, 2015 at 9:23 AM, Jonas Ådahl jad...@gmail.com wrote:
Signed-off-by: Jonas Ådahl jad...@gmail.com
---
hwdb/70-mouse.hwdb | 3 +++
1 file changed, 3 insertions(+)
Applied!
Thanks
David
diff --git a/hwdb/70-mouse.hwdb b/hwdb/70-mouse.hwdb
index 32a8a5d..38afee0 100644
Hi Daniel,
I've got a patch for perl-Net-DBus that adds support for the interactive
authorization stuff currently in dbus-1.9.x branch.
It seems to work well when using it but will need a little polish to
make work nicely when complied against different versions of dbus (e.g.
compiling against
08.01.2015 3:43, Lennart Poettering:
[...]
The fsck of the root file system is done by
systemd-root-fsck.service. It exists both in the initrd and on the
host.
On my box the first check is performed by systemd-fsck@ (I can see it in
the log), and the second by systemd-root-fsck apparently.
08.01.2015 4:12, Cristian Rodríguez:
El 07/01/15 a las 21:43, Lennart Poettering escribió:
Maybe suse forgot to include this service file in the initrd or so?
Correct. It appears to be a bug in the dracut package. I wonder why ..
Ok. So should I file a report to opensuse bugtracker? I have
El 07/01/15 a las 22:55, Nikolai Zhubr escribió:
08.01.2015 4:12, Cristian Rodríguez:
El 07/01/15 a las 21:43, Lennart Poettering escribió:
Maybe suse forgot to include this service file in the initrd or so?
Correct. It appears to be a bug in the dracut package. I wonder why ..
Ok. So
El 07/01/15 a las 22:55, Nikolai Zhubr escribió:
08.01.2015 4:12, Cristian Rodríguez:
El 07/01/15 a las 21:43, Lennart Poettering escribió:
Maybe suse forgot to include this service file in the initrd or so?
Correct. It appears to be a bug in the dracut package. I wonder why ..
Ok. So
Hello!
I seem to have reproduced this issue. After a lot of swapping, systemd
appeared to have become stuck. Trying to restart services with systemctl
blocked indefinitely. Strangely, this seemed to be the case even after a
reboot.
Here is a part of the strace -p 1
recvmsg(16,
2015-01-07 14:24 GMT+01:00 Zbigniew Jędrzejewski-Szmek zbys...@in.waw.pl:
On Wed, Jan 07, 2015 at 01:44:17PM +0100, Michael Biebl wrote:
sysv-generator: initialize units before use to ensure correct
ordering
[..]
I've updated the commit message accordingly. See attached patch.
Looks fine.
Hi,
Looking at bootlog console messages, I noticed something strange.
systemd says:
Expecting device dev-disk-by-x2duuid-4c25...
... and soon adds:
A start job is running for dev-disk-by-x2duuid-4c25...
... and it keeps waiting for some seconds.
Also, systemd-analyze blame lists
After adding the simple udev rule:
--
KERNEL==seq, SUBSYSTEM==sound, TAG+=shared
--
/dev/snd/seq becomes accessible from all seats.
Could you resolve this patch upstream or propose another way
On Wed, Jan 07, 2015 at 01:44:17PM +0100, Michael Biebl wrote:
sysv-generator: initialize units before use to ensure correct
ordering
The original loop called fix_order() on each service immediately after
loading it, but fix_order() would reference other units which were not
loaded yet.
Hi,
Lennart Poettering:
And the various states so far have not been documented on purpose,
since we want to have the liberty to still make alterations to the
state machines. And I am not convinced the time has come yet to set
this in stone and document it.
You might document it but add a
28 matches
Mail list logo
