Le lun. 28 oct. 2019 à 16:49, Andrei POPESCU a
écrit :
> On Mi, 18 sep 19, 14:40:29, Prunk Dump wrote:
> >
> > -> Maybe a bug in the systemd configuration files that awake service
> > in wrong order ? ( I will do soon a not related bug report to Debian,
> > puppet.service does not contain any "Af
On Mi, 18 sep 19, 14:40:29, Prunk Dump wrote:
>
> -> Maybe a bug in the systemd configuration files that awake service
> in wrong order ? ( I will do soon a not related bug report to Debian,
> puppet.service does not contain any "After=" line )
>
> -> Maybe a bug in network-manager when the host
Baptiste, on 2019-09-18:
> So with you help here my current check list :
> -> Maybe a bug in the resolv.conf file access just after the suspend
> recover. I need to find who is accessing the file and when. And why
> this prevent DNS resolution working.
>
> -> Maybe a bug in the systemd configuratio
Thanks you very much Etienne for your help ! I will try to give as
much precision as possible using your tips.
Le mar. 17 sept. 2019 à 23:13, Étienne Mollier
a écrit :
>
> Baptiste, on 2019-09-17:
> > I have two critical systemd services running on my clients :
> > -> "puppet" that ensure propaga
Baptiste, on 2019-09-17:
> I have two critical systemd services running on my clients :
> -> "puppet" that ensure propagation of my whole network configuration.
> -> "samba winbind" that allow users pam authentication and Name Service
> Switch.
> These two services use DNS to find their services s
Hello Debian Team !
I'm the network Administrator of a french High School and I have
troubles debugging a DNS lookup problem affecting all my 550 Debian
Buster clients.
I have two critical systemd services running on my clients :
-> "puppet" that ensure propagation of my whole network configurati
6 matches
Mail list logo
