Hi!
As maintainer been investigating how wsdd is run by gvfs. If wsdd is
already running as a server to support smbd, gvfsd will not be able to
start another wsdd due to the interface multicast socket(s) already
being taken....
I can set the default arguments for wsdd to listen on a socket in say
/var/run/wsdd/wsdd. Is it possible to tell gvfsd to talk to that socket
instead of its one in /run/user/<uid>/gvfsd/wsdd ??
Cheers,
Matt
On 18/02/24 23:20, Laurent Bigonville wrote:
On Fri, 16 Feb 2024 10:04:53 -0500 =?UTF-8?Q?Jeremy_B=C3=ADcha?=
<jeremy.bi...@canonical.com> wrote:
> gvfs 1.53.90-1 uses wsdd to find newer Windows network shares.
>
> My initial understanding is that wsdd can be used both to advertise
> network shares or to find network shares. gvfs only needs the "find"
> behavior and gvfs calls wsdd from $PATH directly when needed.
>
> I believe it is unwanted behavior for wsdd.service to be running for
> gvfs's use case.
>
> Therefore, please create a separate package for wsdd.service , perhaps
> named wsdd-server
Currently all machines installing wsdd start to advertise on the
network and are automatically discoverable, this is less than optimal
indeed.
And other alternative is to pass "--no-enable --no-start" to
dh_installsystemd and add an After/Wants in the packages that really
requires the "server" part to be running?
Not sure what other packages we are talking about here? There is
currently on one rdep and it's gvfs
But I agree the "server" part shouldn't be running by default, at
least without the "--no-host" option
