On Tue, Feb 6, 2018 at 1:21 AM, Peter Hutterer
wrote:
> On Mon, Feb 05, 2018 at 11:51:30AM +0200, Mantas Mikulėnas wrote:
> > On Mon, Feb 5, 2018 at 8:02 AM, Peter Hutterer >
> > wrote:
> >
> > > Hi all,
> > >
> > > I think there is some race conditions between the udev rules and the
> hwdb
> >
On Mon, Feb 05, 2018 at 11:51:30AM +0200, Mantas Mikulėnas wrote:
> On Mon, Feb 5, 2018 at 8:02 AM, Peter Hutterer
> wrote:
>
> > Hi all,
> >
> > I think there is some race conditions between the udev rules and the hwdb
> > and I cannot rely that udev rules are applied consistently on a device.
>
On Mo, 05.02.18 10:21, Johannes Ernst ([email protected]) wrote:
> >> It appears systemd-sysusers does not create home directories. On
> >> the other hand, it picks (largely unpredictable) UIDs from a
> >> range.
> >>
> >> So I have to run systemd-sysusers, and after that, find the UID
> >
On Mon, Feb 05, 2018 at 10:21:17AM -0800, Johannes Ernst wrote:
>
> > On Feb 4, 2018, at 21:56, Michael Chapman wrote:
> >
> > On Mon, 5 Feb 2018, Johannes Ernst wrote:
> >> It appears systemd-sysusers does not create home directories. On the other
> >> hand, it picks (largely unpredictable) UI
Am 05.02.2018 um 19:35 schrieb Johannes Ernst:
On Feb 5, 2018, at 10:31, Zbigniew Jędrzejewski-Szmek wrote:
systemd-sysusers
[[ -d /var/lib/foo ]] && mkdir -m755 /var/lib/foo
chown $(id -u foo):$(id -g foo) /var/lib/foo
# /usr/lib/tmpfiles.d/foo.conf
d /var/lib/foo 0755 foo foo -
(BTW,
> On Feb 5, 2018, at 10:31, Zbigniew Jędrzejewski-Szmek
> wrote:
>> systemd-sysusers
>> [[ -d /var/lib/foo ]] && mkdir -m755 /var/lib/foo
>> chown $(id -u foo):$(id -g foo) /var/lib/foo
>
> # /usr/lib/tmpfiles.d/foo.conf
> d /var/lib/foo 0755 foo foo -
>
> (BTW, chown $(id -u foo):$(id -g f
> On Feb 4, 2018, at 21:56, Michael Chapman wrote:
>
> On Mon, 5 Feb 2018, Johannes Ernst wrote:
>> It appears systemd-sysusers does not create home directories. On the other
>> hand, it picks (largely unpredictable) UIDs from a range.
>>
>> So I have to run systemd-sysusers, and after that, f
On Fr, 02.02.18 19:09, worz ([email protected]) wrote:
Humm, your emails are really weirdly formatted. Generally, sending
HTML email to technical mailing lists is frowned upon, as replying is
very messy. We usually won't complain about this too much, but in this
case I have trouble getting good old mut
I would understand the question as :
"why is the foreground/background concept linked to the concept of scope ?"
for most people --scope means "run in the background" which is only a
side effect of what that command really does.
Maybe there is a need of some doc clarification, or get non-scop
On Fr, 02.02.18 19:00, worz ([email protected]) wrote:
> Hello, I was wondering why systemd-run --scope needs to be
> synchronous, it would be nice if someone could explain what happens
> under the hood, and what prevents it from just putting the process
> in the scope, and maybe just call the Abandon(
hi,
maybe good to know that libgcrypt provides a function which offers "all in one":
void gcry_md_hash_buffer (int algo, void *digest, const void *buffer,
size_t length)
digest can be an array created earlier using the function gcry_md_get_algo_dlen.
Stef
__
On Mon, Feb 5, 2018 at 8:02 AM, Peter Hutterer
wrote:
> Hi all,
>
> I think there is some race conditions between the udev rules and the hwdb
> and I cannot rely that udev rules are applied consistently on a device.
>
> For reference, after building libinput run
> sudo ./build/libinput-test-sui
Am 05.02.2018 um 10:47 schrieb Michael Chapman:
On Mon, 5 Feb 2018, Reindl Harald wrote:
Am 05.02.2018 um 06:56 schrieb Michael Chapman:
On Mon, 5 Feb 2018, Johannes Ernst wrote:
It appears systemd-sysusers does not create home directories. On the
other hand, it picks (largely unpredictab
On Mon, 5 Feb 2018, Reindl Harald wrote:
Am 05.02.2018 um 06:56 schrieb Michael Chapman:
On Mon, 5 Feb 2018, Johannes Ernst wrote:
It appears systemd-sysusers does not create home directories. On the
other hand, it picks (largely unpredictable) UIDs from a range.
So I have to run systemd-s
On Mon, Feb 5, 2018 at 11:26 AM, Reindl Harald
wrote:
>
>
> Am 05.02.2018 um 06:56 schrieb Michael Chapman:
>
>> On Mon, 5 Feb 2018, Johannes Ernst wrote:
>>
>>> It appears systemd-sysusers does not create home directories. On the
>>> other hand, it picks (largely unpredictable) UIDs from a range
On Mon, Feb 05, 2018 at 09:17:52AM +0100, Stef Bon wrote:
> Same error here:
> (gcry_md_open without gcry_md_close)
> line 901 in src/resolve/resolved-dns-sec.c
> while in the same file at 1227 it's done the good way.
Indeed. PR submitted: https://github.com/systemd/systemd/pull/8100.
Zbyszek
___
Am 05.02.2018 um 06:56 schrieb Michael Chapman:
On Mon, 5 Feb 2018, Johannes Ernst wrote:
It appears systemd-sysusers does not create home directories. On the
other hand, it picks (largely unpredictable) UIDs from a range.
So I have to run systemd-sysusers, and after that, find the UID of th
Same error here:
(gcry_md_open without gcry_md_close)
line 901 in src/resolve/resolved-dns-sec.c
while in the same file at 1227 it's done the good way.
Stef
___
systemd-devel mailing list
[email protected]
https://lists.freedesktop.org/
18 matches
Mail list logo
