On Thu, Feb 22, 2024 at 07:43:50PM +0300, Andrei Borzenkov wrote:
> On 22.02.2024 19:09, Max Gautier wrote:
> > Hi,
> >
> > Is it possible when writing a dbus-activable service to provide two
> > separate and independent ways to enable it ?
> >
> > The D-Bus service file would for instance be:
>
Hi Cristian,
I had to look up nss-resolve and indeed both LLMNR and system-resolved are
mentioned in the description. In my test VM, `apt-cache policy` is showing that
libnss-resolve package is installed.
I removed it using `apt purge libnss-resolve` and checked journalctl logs again
while
On Thu, Feb 22, 2024 at 2:09 PM anthony_ful...@trendmicro.com
wrote:
>
> Port 5355 is used for LLMNR and RFC-4795 [4], states in the abstract that
> “LLMNR only operates on the local link” so I think the current behavior of
> contacting hosts on port 5355 is incorrect, especially if that host
Hi systemd-devel,
I wanted to run a concern with systemd-resolved through the mailing list before
opening an issue in the github.com repository. The below behavior does not
reproduce with any other resolver I’ve used before.
I noticed that each time a program calls gethostbyaddr() a connection
On 22.02.2024 19:09, Max Gautier wrote:
Hi,
Is it possible when writing a dbus-activable service to provide two
separate and independent ways to enable it ?
The D-Bus service file would for instance be:
[D-BUS Service]
Name=org.freedesktop.Notifications
Exec=notification-daemon
Hi,
Is it possible when writing a dbus-activable service to provide two
separate and independent ways to enable it ?
The D-Bus service file would for instance be:
[D-BUS Service]
Name=org.freedesktop.Notifications
Exec=notification-daemon
SystemdService=dbus-org.freedesktop.Notifications.service
