[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: New SHM
From: |
Hal Murray |
Subject: |
Re: New SHM |
Date: |
Mon, 23 Jan 2023 01:32:58 -0800 |
mlichvar@redhat.com said:
> gpsd would write to ".sock" as expected, but chronyd/ntpd would need to be
> configured to use ".sock1" and the monitoring application would read from
> ".sock2". That's pretty bad when compared ntpshmmon, which
Would it be reasonable for gpsd to setup another socket when the first one is
busy?
That requires clients to try the second one if the first one is busy.
Plan B is for gpsd to always open 2 and ntpshmmon be hardwried to use the
second one.
--
These are my opinions. I hate spam.
- New SHM, Hal Murray, 2023/01/20
- Re: New SHM, Gary E. Miller, 2023/01/20
- Re: New SHM, Miroslav Lichvar, 2023/01/23
- Re: New SHM,
Hal Murray <=
- Re: New SHM, Miroslav Lichvar, 2023/01/23
- Re: New SHM, Gary E. Miller, 2023/01/23
- Re: New SHM, Hal Murray, 2023/01/23
- Re: New SHM, Gary E. Miller, 2023/01/23
- Re: New SHM, Hal Murray, 2023/01/23
- Re: New SHM, Gary E. Miller, 2023/01/23
- Re: New SHM, Hal Murray, 2023/01/23
- Re: New SHM, Miroslav Lichvar, 2023/01/24