Re: [systemd-devel] systemd services via SSH (-H key)

On Sat, 24.10.15 15:57, Reindl Harald (h.rei...@thelounge.net) wrote: > Am 24.10.2015 um 15:04 schrieb Lennart Poettering: > >Well, I am pretty sure using "#" as separator for that is a really > >untypical syntax. I am not sure it's really such a big improvement > >supporting such a syntax over

Re: [systemd-devel] tty0: Failed to start Login Service - intermittently

On Sun, 25.10.15 09:41, poma (pomidorabelis...@gmail.com) wrote: > > Hi Fi > > Failed to start Login Service - intermittently > produces overall delays and timeouts. Sounds like: https://github.com/systemd/systemd/issues/1505 And everybody is puzzled about it. Lennart -- Lennart

Re: [systemd-devel] mdm display manager in Systemd

Am 26.10.2015 um 03:47 schrieb yan...@iscas.ac.cn: I have a question: the support of mdm display manager in Systemd is not good ,all right? why do you think that systemd needs to support each and every displaymanager directly? it does not and does not need becasue the DM runs on top

Re: [systemd-devel] systemd-nspawn --setenv=SOMETHING=other: What is that for?

Hi Lennart, the ContainerInterface says: "The container manager should set $container_uuid= as environment variable for the container's PID 1 to the container UUID it wants to set." I had expected that to be implemented by not resetting this environment variable when starting whichever service

Re: [systemd-devel] mdm display manager in Systemd

On Mon, 26.10.15 10:47, yan...@iscas.ac.cn (yan...@iscas.ac.cn) wrote: > I have a question: the support of mdm display manager in Systemd is > not good ,all right? I never heard of "mdm", but my suggestion would be to ask the mdm developers about this, not the systemd developers. Lennart --

Re: [systemd-devel] systemd-nspawn --setenv=SOMETHING=other: What is that for?

On Sun, 25.10.15 09:30, Peter Paule (systemd-de...@fedux.org) wrote: > Hi Tobias, > > > Most non-trivial docker images need that. Should I open a feature request > > that makes sense. I asked the same some time ago. It's on their > TODO-list, but at that time they didn't use Github for their

Re: [systemd-devel] target file and executable file relationship doubt

On Mon, 26.10.15 17:06, kennedy (kennedy...@163.com) wrote: > Thanks. I realized that the service file depends on target file. > That "local-fs-pre.target" do nothing ? and then "local-fs.target" need > boot.mount first ? The boot.mount and the other mount they were executed > parallelize ?

Re: [systemd-devel] tty0: Failed to start Login Service - intermittently

On 25.10.2015 09:41, poma wrote: > > Hi Fi > > tty0: Failed to start Login Service - intermittently > produces overall delays and timeouts. > > systemd 227 ... Logind does not break w/ systemd.log_level=debug of course. ___ systemd-devel mailing

Re: [systemd-devel] target file and executable file relationship doubt

Thanks. I realized that the service file depends on target file. That "local-fs-pre.target" do nothing ? and then "local-fs.target" need boot.mount first ? The boot.mount and the other mount they were executed parallelize ? And then arrived at "sysinit.target" , and then start some service

Re: [systemd-devel] Direct systemd-journald event-logs tranmssion to Zabbix\Cacti

Anybody online? 24.10.2015 19:01, Mikhail Kasimov пишет: > Hello! > > There is one more question I try to get a clearness for myself -- direct > systemd-journald event-logs tranmssion to Zabbix\Cacti\other log-collector. > > As I understand nowadays we have such event-logs tranmssion schemas: >

[systemd-devel] target file and executable file relationship doubt

what's the relationship between the target file and the real executable file ? "local-fs-pre.target" ,"local-fs.target" will start which service (will execute which binary file) ? best regards!___ systemd-devel mailing list

Re: [systemd-devel] target file and executable file relationship doubt

On Mon, Oct 26, 2015 at 10:13 AM, kennedy wrote: > what's the relationship between the target file and the real executable > file ? > > "local-fs-pre.target" ,"local-fs.target" will start which service (will > execute which binary file) ? > None. They're .target units –

Re: [systemd-devel] Direct systemd-journald event-logs tranmssion to Zabbix\Cacti

26.10.2015 17:35, Lennart Poettering пишет: > On Mon, 26.10.15 15:54, Mikhail Kasimov (mikhail.kasi...@gmail.com) wrote: > >> Hello Lennart! The main question is not about why rsyslog is >> better/worst compared to systemd-journald. The main question is how to >> transmit journald event-log to

Re: [systemd-devel] Proper way of installing avahi dbus activation file

Am 26.10.2015 um 21:58 schrieb Pacho Ramos: The problem is that reading: https://fedoraproject.org/wiki/Packaging:Systemd#DBus_activation "Note that the creation/removal of the alias symlinks should be done with "systemctl enable" and "systemctl disable" only. You should not create these

Re: [systemd-devel] systemd-227: ForwardDelaySec

On Mon, 26.10.15 19:18, Vlad (vo...@vovan.nl) wrote: > Hello, > > It looks like the ForwardDelaySec sets the bridge parameter in > milliseconds instead of seconds: > - in de *.netdev > > [Bridge] > ForwardDelaySec=1 > > - brctl showstp br0 > > ... > forward delay 0.01

[systemd-devel] Proper way of installing avahi dbus activation file

Hello In some distributions we are needing to run this: ln -s avahi-daemon.service /usr/lib/systemd/system/dbus -org.freedesktop.Avahi.service To get avahi started when needed, otherwise, logs will start to be logged about avahi being unable to be started when, for example, I try to print

Re: [systemd-devel] Proper way of installing avahi dbus activation file

Отправлено с iPhone > 27 окт. 2015 г., в 0:06, Reindl Harald написал(а): > > > >> Am 26.10.2015 um 21:58 schrieb Pacho Ramos: >> The problem is that reading: >> https://fedoraproject.org/wiki/Packaging:Systemd#DBus_activation >> >> "Note that the creation/removal of

Re: [systemd-devel] Direct systemd-journald event-logs tranmssion to Zabbix\Cacti

Hello Lennart! The main question is not about why rsyslog is better/worst compared to systemd-journald. The main question is how to transmit journald event-log to centralized log-server (Zabbix\Cacti\so on) directly, without any additional assistant layers (rsyslog in this case). JSON, HTTP(S)

Re: [systemd-devel] systemd-nspawn --setenv=SOMETHING=other: What is that for?

On Mon, 26.10.15 12:42, Tobias Hunger (tobias.hun...@gmail.com) wrote: > Hi Lennart, > > the ContainerInterface says: "The container manager should set > $container_uuid= as environment variable for the container's PID 1 to > the container UUID it wants to set." > > I had expected that to be

Re: [systemd-devel] Direct systemd-journald event-logs tranmssion to Zabbix\Cacti

On Mon, 26.10.15 15:54, Mikhail Kasimov (mikhail.kasi...@gmail.com) wrote: > Hello Lennart! The main question is not about why rsyslog is > better/worst compared to systemd-journald. The main question is how to > transmit journald event-log to centralized log-server (Zabbix\Cacti\so > on)

Re: [systemd-devel] [HEADSUP] nspawn/networkd: moving from iptables to nftables

On Fri, 29 May 2015 17:49:12 +0200, Lennart Poettering wrote: > Yes, we are aware this is unfortunate, and that many people are still > using iptables. For this reason we would like to make the switch quickly > to ensure not too many users start using the iptables hook-up before it > goes away.

[systemd-devel] systemd-227: ForwardDelaySec

Hello, It looks like the ForwardDelaySec sets the bridge parameter in milliseconds instead of seconds: - in de *.netdev [Bridge] ForwardDelaySec=1 - brctl showstp br0 ... forward delay 0.01 bridge forward delay 0.01 ... I might be wrong, but anyway it would