Lennart, it's absolutely possible this is the case, and as I stated
originally, I'm not sure where fault lies, but just that some issues
happened. I agree, perhaps MySQL/MariaDB should output one line for
each progress step.
On 20 April 2017 at 04:41, Lennart Poettering wrote:
> On Wed, 19.04.17
Dear Lennart & list,
thank you for taking your time to answer (and for systemd :-) )!
(TL;DR -> SOLVED)
On Mittwoch, 19. April 2017 18:37:58 CEST Lennart Poettering wrote:
> > == On the host:
> > $ groupadd -g3777036288 MY_GROUP
>
> Don't do this. If you register the group like this, nspawn w
"Igal @ Lucee.org" :
> Examples I see online use forking [...]
Jonathan de Boyne Pollard:
> ... because they are bad examples.
> Read http://jdebp.eu./FGA/systemd-house-of-horror/tomcat.html .
Andrei Borzenkov:
> Service type simple is the worst possible type as it does not provide
> for any
On 4/19/2017 12:17 PM, Lennart Poettering wrote:
> This isn't precisely new functionality, it has been doing that since
> years. It will synthesize "change" udev events when a process closes a block
> device after writing, so that the changed superblock/partition
> information is properly propagate
18.04.2017 21:35, Jonathan de Boyne Pollard пишет:
> "Igal @ Lucee.org" :
>> Examples I see online use forking [...]
>
> ... because they are bad examples. Read
> http://jdebp.eu./FGA/systemd-house-of-horror/tomcat.html .
Service type simple is the worst possible type as it does not provide
for
On Wed, 19.04.17 15:25, Samuel Williams (space.ship.travel...@gmail.com) wrote:
> I am using MariaDB - and the .service file launches mysqld directly -
> it doesn't use mysqld_safe
>
> Here is the basic config, from Arch linux package:
>
> -- mariadb.service
> ExecStart=/usr/sbin/mysqld $MYSQLD_
On Wed, 19.04.17 12:03, Olaf the Lost Viking (olaf.the.lost.vik...@gmail.com)
wrote:
> == Unexpected behaviour:
> Setting up and running nspawn based containers without any PrivateUsers-
> setting works. The containers run using a random user-id. (Here I seem to
> misunderstand the manual as it
On Wed, 19.04.17 09:01, Phil Susi (ps...@ubuntu.com) wrote:
> On 2/16/2017 12:32 PM, Brian C. Lane wrote:
> > I think the tricky part of that is going to be that when we open the
> > device we don't really know what commands are going to be issued so it
> > needs to be RDWR to allow for all the ot
On 17/04/2017 12:50, Lennart Poettering wrote:
> On Wed, 12.04.17 18:27, Timothée Ravier (sios...@gmail.com) wrote:
>> I would like to make the /proc directory inaccessible for some services.
>> Unfortunately, adding the InaccessiblePaths=/proc option to a service unit
>> will
>> not work.
>
> Hm
On 2/16/2017 12:32 PM, Brian C. Lane wrote:
> I think the tricky part of that is going to be that when we open the
> device we don't really know what commands are going to be issued so it
> needs to be RDWR to allow for all the other possibilities.
I'm sure I have seen a patch floating around some
I just upgraded to Ubuntu 17.04 (systemd 232) where systemd-resolved is
turned on by default, which means DNSSEC validation on by default.
My home network has DNS provided by dnsmasq, and for historical reasons
I set the domain name on all hosts there to 'dague.pvt'.
I tried adding both 'dague.pv
Hi!
On the bug tracker guideline page it said that the systemd-devel-list
is also meant for support, so I hope it's okay to ask here this beginnger's
question:
== Environment:
- systemd-232 (systemd-232-22_amd64)
- Debian Stretch (minbase + systemd + systemd-container + ...)
== Goal:
Dear systemd folks,
I am trying to figure out why `systemd-timesyncd` takes quite some
time, that means over 100 ms, to start up on several systems [1]. This
is also reproducible with systemd 232 from Debian Sid/unstable.
After adding `log_info()` statements to the source code, as told in
#syst.
13 matches
Mail list logo
