Re: [systemd-devel] systemd-nspawn network-interface

2017-04-18 Thread poma
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= >>

[systemd-devel] Service Type for Tomcat

2017-04-18 Thread Igal @ Lucee.org
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

Re: [systemd-devel] Service Type for Tomcat

2017-04-18 Thread Tomasz Torcz
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

Re: [systemd-devel] Service Type for Tomcat

2017-04-18 Thread Mantas Mikulėnas
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,

Re: [systemd-devel] Service Type for Tomcat

2017-04-18 Thread Igal @ Lucee.org
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

Re: [systemd-devel] Service Type for Tomcat

2017-04-18 Thread 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 . ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org

Re: [systemd-devel] feature request: implement macsec interface configuration in systemd-networkd

2017-04-18 Thread Tomasz Torcz
On Mon, Apr 17, 2017 at 01:46:29PM +, george Nopicture 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 automatic

Re: [systemd-devel] journal fragmentation on Btrfs

2017-04-18 Thread Lennart Poettering
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

Re: [systemd-devel] feature request: implement macsec interface configuration in systemd-networkd

2017-04-18 Thread Lennart Poettering
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

Re: [systemd-devel] journal fragmentation on Btrfs

2017-04-18 Thread Lennart Poettering
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

[systemd-devel] [nspawn] devpts not mounted with PrivateUsers

2017-04-18 Thread Olaf the Lost Viking
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 + ...) ==

Re: [systemd-devel] My experience with MySQL and systemctl

2017-04-18 Thread Samuel Williams
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

Re: [systemd-devel] My experience with MySQL and systemctl

2017-04-18 Thread Samuel Williams
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