Re: [systemd-devel] How to start a service when a device is created under /dev/pts/

2023-02-13 Thread Mantas Mikulėnas
On Mon, Feb 13, 2023 at 5:16 PM Giuseppe Sacco wrote: > Hello Mantas, > > Il giorno lun, 13/02/2023 alle 14.32 +0100, Giuseppe Sacco ha scritto: > > Il giorno lun, 13/02/2023 alle 15.25 +0200, Mantas Mikulėnas ha scritto: > > > On Mon, Feb 13, 2023 at 3:21 PM Giuseppe Sacco > > > wrote: > > > >

Re: [systemd-devel] How to start a service when a device is created under /dev/pts/

2023-02-13 Thread Giuseppe Sacco
Hello Mantas, Il giorno lun, 13/02/2023 alle 14.32 +0100, Giuseppe Sacco ha scritto: > Il giorno lun, 13/02/2023 alle 15.25 +0200, Mantas Mikulėnas ha scritto: > > On Mon, Feb 13, 2023 at 3:21 PM Giuseppe Sacco > > wrote: > > > [...] > > > In this scenario, the ptys are created by software like i

Re: [systemd-devel] How to start a service when a device is created under /dev/pts/

2023-02-13 Thread Giuseppe Sacco
Il giorno lun, 13/02/2023 alle 15.25 +0200, Mantas Mikulėnas ha scritto: > On Mon, Feb 13, 2023 at 3:21 PM Giuseppe Sacco > wrote: > > [...] > > In this scenario, the ptys are created by software like iaxmodem > > (that uses > > asterisk) when its daemon starts. Some more information is available

Re: [systemd-devel] How to start a service when a device is created under /dev/pts/

2023-02-13 Thread Mantas Mikulėnas
On Mon, Feb 13, 2023 at 3:21 PM Giuseppe Sacco wrote: > Il giorno lun, 13/02/2023 alle 12.12 +0200, Mantas Mikulėnas ha > scritto:[...] > > I'm not entirely sure whether it even makes sense for a .service unit > > to wait for a specific pty? I mean, the entire design of ptys is that > > they're a

Re: [systemd-devel] How to start a service when a device is created under /dev/pts/

2023-02-13 Thread Giuseppe Sacco
Il giorno lun, 13/02/2023 alle 12.12 +0200, Mantas Mikulėnas ha scritto:[...] > I'm not entirely sure whether it even makes sense for a .service unit > to wait for a specific pty? I mean, the entire design of ptys is that > they're assigned on a first-come basis and there's no way for a process > t

Re: [systemd-devel] Extend systemd-resolved service to override DNS response

2023-02-13 Thread Kevin P. Fleming
On Mon, Feb 13, 2023, at 05:38, Aditya Sharma wrote: > Hi All, > > We needed help in understanding how systemd-resolved service can be extended > to cache DNS responses to protect against DNS server failures. > We were planning to maintain a cache so that we can override negative > responses fro

[systemd-devel] Extend systemd-resolved service to override DNS response

2023-02-13 Thread Aditya Sharma
Hi All, We needed help in understanding how systemd-resolved service can be extended to cache DNS responses to protect against DNS server failures. We were planning to maintain a cache so that we can override negative responses from the DNS server and replace it with our cached last known good rec

Re: [systemd-devel] User wayland session, conceptual questions

2023-02-13 Thread Mantas Mikulėnas
On Sun, Feb 12, 2023 at 9:27 AM Vladimir Kudrya wrote: > On 10/02/2023 12.51, Mantas Mikulėnas wrote: > > Also systemd.special manual recommends putting display servers into >> session.slice. But in case of a wayland compositor it is impossible to >> separate it from the apps, because the composi

Re: [systemd-devel] How to start a service when a device is created under /dev/pts/

2023-02-13 Thread Mantas Mikulėnas
On Mon, Feb 13, 2023 at 11:12 AM Giuseppe Sacco wrote: > Hello, > I am working on hylafax, a program for sending and receiving faxes, and I > am facing a problem when it should wait for a device that is not in /dev/ > but in /dev/pts/. It seems that udev events only cover device creation in > /de

[systemd-devel] How to start a service when a device is created under /dev/pts/

2023-02-13 Thread Giuseppe Sacco
Hello, I am working on hylafax, a program for sending and receiving faxes, and I am facing a problem when it should wait for a device that is not in /dev/ but in /dev/pts/. It seems that udev events only cover device creation in /dev/ and are not fired when the device appear in /dev/pts. This is a