Re: [systemd-devel] [SPAM] Re: Custom options and passing options via command line.

Lennart Poettering writes: > On Di, 10.05.22 17:59, Kamil Jońca (kjo...@op.pl) wrote: > >> Maybe I was not clear. >> I have ("internal") interfaces qemu1 and qemu2. and interface eth >> ("external") >> I wat to nat traffic from interface qem

Re: [systemd-devel] [SPAM] Re: Custom options and passing options via command line.

Lennart Poettering writes: > On Mo, 09.05.22 20:00, Kamil Jońca (kjo...@op.pl) wrote: > >> Kamil Jońca writes: >> >> >> > Let's see. >> > from SYSTEMD.NETWORK(5) >> > ... >> > IPMasquerade= >> >Configures IP masque

Re: [systemd-devel] [SPAM] Re: Custom options and passing options via command line.

Lennart Poettering writes: > On Di, 10.05.22 12:00, Kamil Jońca (kjo...@op.pl) wrote: > >> > The engine is decided at build time, i.e. can be either iptables or >> > nftables. >> >> But there are two kind of "nat' in *tables suites: 1.masquerade

Re: [systemd-devel] [SPAM] Re: Custom options and passing options via command line.

Lennart Poettering writes: > On Mo, 09.05.22 19:13, Kamil Jońca (kjo...@fastmail.com) wrote: > >> >> 3. decide where to resolve names based on domain and existence of ipsec >> >> or openvpn tunnel. >> > >> > Sounds like a job for the resolved

Re: [systemd-devel] [SPAM] Re: Custom options and passing options via command line.

(sent previously from different address) Lennart Poettering writes: > On Mo, 09.05.22 18:12, Kamil Jońca (kjo...@op.pl) wrote: > >> For now I do not know how handle multiple interface where: >> 1. set routing according to classles routes from dhcp on some >> int

Re: [systemd-devel] [SPAM] Re: Custom options and passing options via command line.

Kamil Jońca writes: > Let's see. > from SYSTEMD.NETWORK(5) > ... > IPMasquerade= >Configures IP masquerading for the network interface. If >enabled, packets forwarded from the network interface will be >appear as coming from the local

Re: [systemd-devel] Custom options and passing options via command line.

Lennart Poettering writes: [...] >> >> I am afraid you will not cover all cases with networking. > > Well, I am not sure. I am pretty sure there are almost always better > ways to fix the issues that people address with network callout stuff. I cannot discuss with your conviction. For now I do

Re: [systemd-devel] Custom options and passing options via command line.

Lennart Poettering writes: > On So, 08.05.22 19:19, Kamil Jońca (kjo...@op.pl) wrote: > >> I have question about custom options in network interface definitions >> and passing it via command line. >> In currend Debian tools >> >> (https://manpages.debian.org/

[systemd-devel] Custom options and passing options via command line.

I have question about custom options in network interface definitions and passing it via command line. In currend Debian tools (https://manpages.debian.org/buster/ifupdown/interfaces.5.en.html) there is a possibility to define custom option and passing it to up/down script (see ENVIRONMENT

[systemd-devel] network interface scripting

Hello. Current situation: debian laptop with interfaces defined in /etc/network/interfaces + resolvconf + dnsmasq packages and bunch of scripts wchich configures network (routes and name resolving) according to interfaces and vpn up down. For example 1. I am connected to home1 network

Re: [systemd-devel] delayed start 'on calendar' timers - is it possible?

Lennart Poettering writes: > On Do, 13.12.18 21:56, Kamil Jońca (kjo...@o2.pl) wrote: > >> Lennart Poettering writes: >> >> [...] >> > >> > What do you mean by "run immediately"? Are you saying the service the >> > timer is suppos

[systemd-devel] delayed start 'on calendar' timers - is it possible?

Assume, we want to create "OnCalendar" timer. and for example we want to run it at 5:0 AM. (ie. OnCalendar=*-*-* 5:0) How can I add this timer WITHOUT immediate running? is systemctl enable "timer" enough? When I issue "systemctl start timer", this timer run immediately. KJ --

Re: [systemd-devel] Does user timer start at boot?

Lennart Poettering writes: > On Di, 02.10.18 17:14, Kamil Jońca (kjo...@o2.pl) wrote: > >> So I cannot run ONLY user timers? >> (IE i have some services which I want only on user login, but I want to >> use timers at boot?) > > Well, depends how you login hap

Re: [systemd-devel] Does user timer start at boot?

Lennart Poettering writes: > On Di, 02.10.18 16:25, Kamil Jońca (kjo...@o2.pl) wrote: > >> >> >> I do not know if I not overlooked something. >> >> But my question is: >> Does "--user" timer start at boot like user cron entries? > > N

[systemd-devel] Does user timer start at boot?

I do not know if I not overlooked something. But my question is: Does "--user" timer start at boot like user cron entries? KJ -- http://wolnelektury.pl/wesprzyj/teraz/ It is better to never have tried anything than to have tried something and failed. -- motto of jerks, weenies

Re: [systemd-devel] exim4 only queues mails sent by systemd service

kjo...@o2.pl (Kamil Jońca) writes: [...] > And another question: is it a way to make systemd not to kill background > processes? Sorry for premature question. I just read about KillMode setting. KJ -- http://wolnelektury.pl/wesprzyj/teraz/ "Maybe we can get together and show off to

Re: [systemd-devel] exim4 only queues mails sent by systemd service

kjo...@o2.pl (Kamil Jońca) writes: > Lennart Poettering writes: > >> On Mo, 24.09.18 20:34, Kamil Jońca (kjo...@o2.pl) wrote: >>> > This didn't work well enough IIRC, but if it did, then it'd provide >>> > almost postfix-like architecture. >&g

Re: [systemd-devel] exim4 only queues mails sent by systemd service

Lennart Poettering writes: > On Mo, 24.09.18 20:34, Kamil Jońca (kjo...@o2.pl) wrote: >> > This didn't work well enough IIRC, but if it did, then it'd provide >> > almost postfix-like architecture. >> > >> > Or just making 'sendmail' send a SIGALRM to

Re: [systemd-devel] exim4 only queues mails sent by systemd service

Mantas Mikulėnas writes: [...] > > This didn't work well enough IIRC, but if it did, then it'd provide > almost postfix-like architecture. > > Or just making 'sendmail' send a SIGALRM to the main daemon would do the job > perfectly well, I suspect... > > -- > Mantas Mikulėnas But I

Re: [systemd-devel] exim4 only queues mails sent by systemd service

Lennart Poettering writes: > On Mo, 24.09.18 12:04, Mantas Mikulėnas (graw...@gmail.com) wrote: > >> > Uh, this looks like something you need to ask the exim community, >> > systemd can't make exim mail queueing decisions, that's entirely >> > internal to exim. >> > >> > One question though: are

Re: [systemd-devel] exim4 only queues mails sent by systemd service

Michael Biebl writes: > Am So., 23. Sep. 2018 um 22:49 Uhr schrieb Kamil Jońca : [...] > > Fwiw, I tried your example service file, works for me. To be clear: Message was delivered at once; not put in queue, and delivered in queue run? KJ -- http://wolnelektury.pl/wesprzyj/teraz/

Re: [systemd-devel] exim4 only queues mails sent by systemd service

Lennart Poettering writes: > On So, 23.09.18 22:48, Kamil Jońca (kjo...@o2.pl) wrote: > >> It is something strange with sending mails from systemd system service: >> assume we have service file /etc/systemd/system/mailtest.service: >> >> --8<--

[systemd-devel] exim4 only queues mails sent by systemd service

It is something strange with sending mails from systemd system service: assume we have service file /etc/systemd/system/mailtest.service: --8<---cut here---start->8--- [Unit] Description="Test maili" [Service] #User=kjonca NoNewPrivileges=false Type=oneshot

Re: [systemd-devel] systemd user unit - how to prepare environment?

Lennart Poettering writes: [...] >> > >> > (i.e. I would to have PATH=$PATH:xxx) > > You can add them to ~/.config/systemd/user.conf in the Environment= > field in the [Manager] section, see systemd-system.conf(5).x Two questions: 1. Can I there use construct like PATH=$PATH:xxx? 2. whether

Re: [systemd-devel] systemd user unit - how to prepare environment?

I post on debian-user, but no answer. Maybe here I found some knowledge. KJ kjo...@poczta.onet.pl (Kamil Jońca) writes: > I tried to setup some user units in my desktop, and have problem with > env variables. > So far I set them up in custom .xsession file (in home directory) > I

Re: [systemd-devel] AmbientCapabilities working examples?

Mantas Mikulėnas <graw...@gmail.com> writes: > On Mon, Sep 4, 2017, 21:42 Kamil Jońca <kjo...@o2.pl> wrote: > > I try to configure my freeradius service with capabilities > (https://lists.debian.org/debian-devel/2017/09/msg00062.html) > > i ca

[systemd-devel] AmbientCapabilities working examples?

I try to configure my freeradius service with capabilities (https://lists.debian.org/debian-devel/2017/09/msg00062.html) i can do with setting capabilities on freeradius binary. But I headr about AmbientCapabilities directive and I tried to use it. Without success - freeradius dhcp server

Re: [systemd-devel] systemd - how to run system service by user target

Lennart Poettering writes: [...] > > Well, this would require a privilege elevation. You can configure that > by invoking "systemctl start --system" on the right system units, and > then telling PK via its policy language that your user shall be > allowed to do that. But

[systemd-devel] systemd - how to run system service by user target

Assume we have openvpn.service. This service neccessary only when I want to connect to my work from home. Is it possible to make user target which will be automatically run this service? KJ -- http://wolnelektury.pl/wesprzyj/teraz/ Alas, I am dying beyond my means. -- Oscar