On 22.10.21 09:08, Josef Moellers wrote:
> Hi,
> I'm working on bind/named and I'm currently trying to find out why
> starting of named fails.
> When I run "systemctl start named", I get these lines in the journal:
> Oct 22 09:02:05 sles15-sp4 systemd[2012]:
Hi,
I'm working on bind/named and I'm currently trying to find out why
starting of named fails.
When I run "systemctl start named", I get these lines in the journal:
Oct 22 09:02:05 sles15-sp4 systemd[2012]: Failed to determine whether
/run/systemd/unit-root/run/named is already a mount point:
No s
On 03.03.20 12:26, Ilya Matveychikov wrote:
> Dear Lennart,
>
> Thank you for the reply.
>
>> On Mar 3, 2020, at 12:54 PM, Lennart Poettering
>> wrote:
>>
>> On Mo, 02.03.20 00:35, Ilya Matveychikov (matvejchi...@gmail.com) wrote:
>>
>>> Hey guys,
>>>
>>> I’m not sure is it the right place to a
On 13.06.19 12:18, Andrei Borzenkov wrote:
> 13.06.2019 11:11, Josef Moellers пишет:
>> On 12.06.19 17:34, Andrei Borzenkov wrote:
> ...
>>>
>>> If I add pam_keyinit to systemd-user, I do get session keyring for gnome
>>> terminal, but this is really wron
On 12.06.19 17:34, Andrei Borzenkov wrote:
> 11.06.2019 15:32, Josef Moellers пишет:
>> On 11.06.19 13:27, Mantas Mikulėnas wrote:
>>> On Tue, Jun 11, 2019 at 1:58 PM Josef Moellers >
>>> The point is that in the gnome-terminal case, pam_keyinit.so is not
>&
On 11.06.19 14:32, Josef Moellers wrote:
> On 11.06.19 13:27, Mantas Mikulėnas wrote:
>> On Tue, Jun 11, 2019 at 1:58 PM Josef Moellers
>> The point is that in the gnome-terminal case, pam_keyinit.so is not
>> involved.
>>
>>
>> It is. The systemd
On 11.06.19 13:27, Mantas Mikulėnas wrote:
> On Tue, Jun 11, 2019 at 1:58 PM Josef Moellers The point is that in the gnome-terminal case, pam_keyinit.so is not
> involved.
>
>
> It is. The systemd --user instance (from which dbus-daemon and
> gnome-terminal-server de
On 11.06.19 12:45, Mantas Mikulėnas wrote:
> On Tue, Jun 11, 2019 at 1:08 PM Josef Moellers <mailto:jmoell...@suse.de>> wrote:
>
> Hi,
>
> We have seen this problem: when you open a gnome-terminal, then the
> shell in that terminal will not have t
Hi,
We have seen this problem: when you open a gnome-terminal, then the
shell in that terminal will not have the same keyring (created by
pam_keyinit.so) as the one eg in an xterm. This is due to the fact that
the xterm ist started by the standard fork/exec mechanism which passes
the keyring down
On 04.06.19 13:32, Ulrich Windl wrote:
> Hi!
>
> I have a question for ConditionPathExists:
> If I specify two files like "ConditionPathExists=/etc/idredir.conf
> /etc/isredir.conf", I get a "start condition failed" even if both files exist.
>
> There's also some confusion where exactly a pipe
On 28.05.19 16:59, Lennart Poettering wrote:
> On Di, 28.05.19 14:04, Josef Moellers (jmoell...@suse.de) wrote:
>
>>> Regarding the syscall groupings: yes, the groups exist precisely to
>>> improve cases like this. That said, I think we should be careful not
>>>
On 28.05.19 16:59, Lennart Poettering wrote:
> On Di, 28.05.19 14:04, Josef Moellers (jmoell...@suse.de) wrote:
>
>>> Regarding the syscall groupings: yes, the groups exist precisely to
>>> improve cases like this. That said, I think we should be careful not
>>>
On 28.05.19 13:57, Lennart Poettering wrote:
> On Di, 28.05.19 11:43, Josef Moellers (jmoell...@suse.de) wrote:
>
>> Hi,
>>
>> We just had an issue with a partner who tried to filter out the "open"
>> system call:
>>
>> . This may, in gene
On 28.05.19 12:25, Martin Wilck wrote:
> On Tue, 2019-05-28 at 11:43 +0200, Josef Moellers wrote:
>> Hi,
>>
>> We just had an issue with a partner who tried to filter out the
>> "open"
>> system call:
>>
>> . This may, in general, not be a ver
Hi,
We just had an issue with a partner who tried to filter out the "open"
system call:
. This may, in general, not be a very clever idea because how is one to
load a shared library to start with, but this example has revealed
something problematic ...
SystemCallFilter=~open
The problem t
On 18.04.19 18:17, Felipe Sateler wrote:
> On Thu, 18 Apr 2019 14:21:09 +0200, Josef Moellers wrote:
>
>> Hi,
>>
>> We're currently working on a bug which afaict is due to a race
>> condition:
>>
>> 1) systemd starts xenstored.service
>> 2) /
On 18.04.19 15:35, Lennart Poettering wrote:
> On Do, 18.04.19 14:21, Josef Moellers (jmoell...@suse.de) wrote:
>
>> Hi,
>>
>> We're currently working on a bug which afaict is due to a race condition:
>>
>> 1) systemd starts xenstored.service
>> 2)
Hi,
We're currently working on a bug which afaict is due to a race condition:
1) systemd starts xenstored.service
2) /etc/xen/scripts/launch-xenstore does its work (starts
/usr/lib/xen/bin/init-xenstore-domain)
3) /etc/xen/scripts/launch-xenstore runs "systemd-notify --ready"
4) "systemd-notify -
18 matches
Mail list logo
