[systemd-devel] (no subject)

stop putting this useless shit in dmesg out-of-date, rotating. [60542.641705] systemd-journald[493]: Data hash table of /run/log/journal/8432ddf2a6da4319b318e6e27319f059/system.journal has a fill level at 75.0 (7568 of 10090 items, 5812224 file size, 768 bytes per hash table item), suggesting

Re: [systemd-devel] (no subject)

On Tue, Oct 17, 2023 at 7:33 AM Tim Richardson wrote: > There is a long standing and long bug report in Ubuntu which attributes > the inability to start the Firefox snap (or any snap with sandboxing) to > snapd. > In fact, the users having this problem mostly have in common that their > session

[systemd-devel] (no subject)

There is a long standing and long bug report in Ubuntu which attributes the inability to start the Firefox snap (or any snap with sandboxing) to snapd. In fact, the users having this problem mostly have in common that their session is started with a remote desktop session. such as nomachine

[systemd-devel] (no subject)

Sascha Daoudia

[systemd-devel] (no subject)

Okay

[systemd-devel] (no subject)

S. Dadudida

[systemd-devel] (no subject)

[systemd-devel] (no subject)

Dec 1 04:39:04 vmi1027878 systemd: Starting Web server Apache... Dec 1 04:39:10 vmi1027878 kernel: Firewall: *TCP_IN Blocked* IN=eth0 OUT= MAC=00:50:56:48:14:f9:74:83:ef:4e:ae:4b:08:00 SRC=67.11.199.196 DST=38.242.209.222 LEN=60 TOS=0x00 PREC=0x00 TTL=53 ID=64136 DF PROTO=TCP SPT=57544 DPT=30303

[systemd-devel] (no subject)

unsuscribe -- *ri* *Ricardo Elías Giraldo Gärtner* ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] (no subject)

Ok ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] (no subject)

Use this email ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] firewalld subject: allowing icmp echo-request

On Fr, 06.12.19 12:17, Andy Pieters (syst...@andypieters.me.uk) wrote: > Hi everyone > > This is on Centos 7.7.1908 and firewalld 0.6.3 > > I could not find a firewalld-specific mailing list and I hope it is ok > to ask it here. This is the systemd mailing list. There's no overlap between

Re: [systemd-devel] firewalld subject: allowing icmp echo-request

On Fri, 6 Dec 2019 at 13:08, Kenneth Porter wrote: > > --On Friday, December 06, 2019 12:17 PM + Andy Pieters > wrote: > > > This is on Centos 7.7.1908 and firewalld 0.6.3 > > > > I could not find a firewalld-specific mailing list and I hope it is ok > > to ask it here. > > firewalld list is

Re: [systemd-devel] firewalld subject: allowing icmp echo-request

--On Friday, December 06, 2019 12:17 PM + Andy Pieters wrote: This is on Centos 7.7.1908 and firewalld 0.6.3 I could not find a firewalld-specific mailing list and I hope it is ok to ask it here. firewalld list is here. It's been pretty quiet lately.

[systemd-devel] firewalld subject: allowing icmp echo-request

Hi everyone This is on Centos 7.7.1908 and firewalld 0.6.3 I could not find a firewalld-specific mailing list and I hope it is ok to ask it here. I wanted to allow pings on a LAN server and have tried a number [1] of [2] different [3] things[4]. After adding the direct rules and inspecting the

Re: [systemd-devel] (no subject)

On Fr, 19.01.18 18:16, Reindl Harald (h.rei...@thelounge.net) wrote: > if you don't bother to write a subject it can't be that important Reindl, it's not necessary to constantly write such snarky replies. Please be more friendly if mailing list submissions aren't up to your standards right-away.

Re: [systemd-devel] (no subject)

Am 19.01.2018 um 18:22 schrieb Matt Zagrabelny: On Fri, Jan 19, 2018 at 11:16 AM, Reindl Harald > wrote: if you don't bother to write a subject it can't be that important Sometimes people make mistakes. Like forgetting to enter a

Re: [systemd-devel] (no subject)

On Fri, Jan 19, 2018 at 11:16 AM, Reindl Harald wrote: > if you don't bother to write a subject it can't be that important > Sometimes people make mistakes. Like forgetting to enter a subject. Don't assume the worst. -m ___

Re: [systemd-devel] (no subject)

if you don't bother to write a subject it can't be that important ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] (no subject)

I am trying to use "sd_watchdog_enabled".  If I run my service without forking, the sd_watchdog_enabled function works as expected: Jan 18 15:05:29 thinkpad systemd[1]: Starting WaitonlyServer... Jan 18 15:05:30 thinkpad waitonly[11172]: PID before fork  = 11172 Jan 18 15:05:30 thinkpad

[systemd-devel] (no subject)

From graw...@gmail.com Sat Aug 22 17:58:23 2015 MIME-Version: 1.0 References: 55d850ac.2050...@poczta.onet.pl In-Reply-To: 55d850ac.2050...@poczta.onet.pl Message-ID: CAPWNY8XAt8SebPVd3ZOJ46rzcg=kmv68wujoazou7_hgzia...@mail.gmail.com Date: Sat, 22 Aug 2015 14:58:24 + Subject: Re: [systemd

[systemd-devel] (no subject)

Hello,   My name is Andrey. I would like to activate a service by socket or D-Bus and stop it when unneeded. The activation works fine but I failed to find a way how the service can be stopped/deactivated automatically when it is no longer needed by using applications. Would you please help

Re: [systemd-devel] (no subject)

On Tue, 02.12.14 23:50, Andrey Shinkevich (andys...@mail.ru) wrote: Heya, My name is Andrey. I would like to activate a service by socket or D-Bus and stop it when unneeded. The activation works fine but I failed to find a way how the service can be stopped/deactivated automatically when it

[systemd-devel] (no subject)

konstantin...@yandex.ru ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] (no subject)

Hello. I tried to execute a process by using socket activation. As it is referred at systemd manual, I made server and client process by using sd-daemon.h and sd-daemon.c. when I made those processes, I used UDS(Unix Domain Socket) to make communication between server and client. (I also made

Re: [systemd-devel] (no subject)

I replied in the thread with a subject line. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] (no subject)

Signed-off-by: Yang Zhiyong yangzy.f...@cn.fujitsu.com --- src/udev/udevadm-settle.c | 15 --- 1 files changed, 12 insertions(+), 3 deletions(-) mode change 100644 = 100755 src/udev/udevadm-settle.c diff --git a/src/udev/udevadm-settle.c b/src/udev/udevadm-settle.c old mode 100644

Re: [systemd-devel] (no subject)

On 10/22/2013 05:03 PM, Yang Zhiyong wrote: Signed-off-by: Yang Zhiyong yangzy.f...@cn.fujitsu.com You missed the patch subject and change log. Thanks, Wanlong Gao --- src/udev/udevadm-settle.c | 15 --- 1 files changed, 12 insertions(+), 3 deletions(-) mode change 100644 =

[systemd-devel] (no subject)

Here is my new attempt for interface naming for cards in non-zero domains. Oddly enough, I still get an f0 at the end of mine even though it is not PCI multifunction. sean@hanyuu ~ $ udevadm test-builtin net_id /sys/class/net/enP2p32s15f0 2/dev/null | grep PATH ID_NET_NAME_PATH=enP2p32s15

Re: [systemd-devel] no subject

On Wed, 17.10.12 16:16, Dennis Semakin (insan...@yandex.ru) wrote: Hi, I'm currently compiling systemd-194. Very often I get the error about undeclarated definitions MS_REC, MS_PRIVATE, MS_MOVE... in mount func. I know that's because of old glibc headers... But. may be it would be useful

Re: [systemd-devel] (no subject)

On Mon, 03.09.12 23:46, Colin Guthrie (co...@mageia.org) wrote: Hi, Heya, OK, so these are the changes I'd propose to fix the issues mentioned in this thread. I've not tested them so this is more for general feedback as to whether this approach is generally a good one or not. The

Re: [systemd-devel] (no subject)

'Twas brillig, and Lennart Poettering at 12/09/12 07:34 did gyre and gimble: On Mon, 03.09.12 23:46, Colin Guthrie (co...@mageia.org) wrote: Hi, Heya, OK, so these are the changes I'd propose to fix the issues mentioned in this thread. I've not tested them so this is more for general

[systemd-devel] (no subject)

Hi, OK, so these are the changes I'd propose to fix the issues mentioned in this thread. I've not tested them so this is more for general feedback as to whether this approach is generally a good one or not. The initial patch is just extra debugging I added to try and work out why my gdm session

Re: [systemd-devel] (no subject)

'Twas brillig, and Colin Guthrie at 03/09/12 23:46 did gyre and gimble: Hi, OK, so these are the changes I'd propose to fix the issues mentioned in this thread. I've not tested them so this is more for general feedback as to whether this approach is generally a good one or not. The