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_OPTS $_WSREP_NEW_CLUSTER
$_WSREP_START_POSITION
ExecStartPost=/bin/sh -c "systemctl unset-envir
Also, it was me sending SIGKILL, not systemctl. systemctl sent SIGTERM
and then finished. But process is still running, so system ended up in
weird state.
On 19 April 2017 at 15:25, Samuel Williams
wrote:
> I am using MariaDB - and the .service file launches mysqld directly -
> it doesn't use mys
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:
"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 .
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedeskto
On Tue, Apr 18, 2017 at 8:44 PM, Igal @ Lucee.org wrote:
> I've read about the difference between "forking" and "notify", but am not
> sure how it really applies in real life.
>
> Can someone tell me what would be the consequences of setting Tomcat (or
> any Java-based service, for that matter) t
On 4/18/2017 10:58 AM, Mantas Mikulėnas wrote:
For example, with Type=forking, systemd expects the main process to
"fork into background" (daemonize) once it's ready. Similarly, if you
use Type=notify, systemd will wait for "READY=1" to be sent over a
Unix socket.
Tomcat does not seem to have
On Tue, Apr 18, 2017 at 10:44:59AM -0700, Igal @ Lucee.org wrote:
> I've read about the difference between "forking" and "notify", but am not
> sure how it really applies in real life.
>
> Can someone tell me what would be the consequences of setting Tomcat (or any
> Java-based service, for that m
I've read about the difference between "forking" and "notify", but am
not sure how it really applies in real life.
Can someone tell me what would be the consequences of setting Tomcat (or
any Java-based service, for that matter) to Type=notify instead of
Type=forking? Examples I see online us
On 17.04.2017 11:59, Lennart Poettering wrote:
> On Thu, 13.04.17 16:08, poma (pomidorabelis...@gmail.com) wrote:
>
>> Hello
>>
>> Regaining of the network-interface, as is stated in the manual, ain't
>> happening;
>> man 1 systemd-nspawn
>> ...
>> OPTIONS
>> ...
>> --network-interface=
>> Assi
On Mon, 17.04.17 21:50, Chris Murphy (li...@colorremedies.com) wrote:
> >> Why do I see so many changes to the journal file, once ever 2-5
> >> seconds? This adds 4096 byte blocks to the file each time, and when
> >> cow, that'd explain why there are so many fragments.
> >>
> >
> >
> > What exactl
On Mon, 17.04.17 13:46, george Nopicture (mad-proffes...@hotmail.com) wrote:
> Are there any plans on implementing macsec interface configuration from
> systemd-networkd? Since its already added in kernel as a loadable
> module, fedora misses a patched iproute2 to support macsec and also
> lacks a
On Mon, 17.04.17 13:49, Chris Murphy (li...@colorremedies.com) wrote:
> On Mon, Apr 17, 2017 at 11:27 AM, Andrei Borzenkov
> wrote:
> > 17.04.2017 19:25, Chris Murphy пишет:
> >> This explains one system's fragmented journals; but the other system
> >> isn't snapshotting journals and I haven't f
12 matches
Mail list logo