Hi Seth, I have an older probe, and I wasn't aware I needed to update its software. How do we do that?
Best, -Michael On Sat, Jan 7, 2023 at 6:03 AM Seth David Schoen <[email protected]> wrote: > Hi, > > I recently posted two threads ultimately related to the same question, > where it turned out that a feature I wanted to use was present in the > current software probe release, but not in the old version that I had > installed. It was indeed relatively easy to upgrade (as a reply on > this list predicted, the upgrade didn't break anything or require any > reconfiguration). > > But I'd still say "relatively easy", because, on the other hand, the > upgrade wasn't managed through my OS package manager like the rest of > the software on my VPS server. > > It appears to me that a lot of software probes (like mine was until > recently!) are still running whichever software probe version was > current when they were first deployed. After all, I don't believe > there's automatic software upgrade functionality in the methods that > most people are using to deploy these. > > Is that true from the point of view of the rest of the Atlas community? > Is there anything that might usefully be done to encourage people to > upgrade periodically? (For example, either sending some kind of e-mail > reminder, or distributing probe software via OS package managers, or > even including a mechanism in the probe client itself by which it could > upgrade itself -- even if as an opt-in feature?) > > -- > ripe-atlas mailing list > [email protected] > https://lists.ripe.net/mailman/listinfo/ripe-atlas >
-- ripe-atlas mailing list [email protected] https://lists.ripe.net/mailman/listinfo/ripe-atlas
