Re:Memory Leaks Detection Paper Co-Authored by Netflix CEO R...
by eschneider on Monday December 05, 2022 @05:46AM
(#33863875)
It would talk to your local license server, but it was definitely NOT communicating back to corporate.
Re:Memory Leaks Detection Paper Co-Authored by Netflix CEO R...
by neilv on Monday December 05, 2022 @06:34AM
(#33864238)
What timeframe are you talking about?
I could be mistaken, since I no longer have the files from close to 30 years ago.
But I did think I saw a case in which it would try to email corporate about using too many seats.
It was memorable because that's the first time I saw that, and it seemed clever but invasive.
Re:Memory Leaks Detection Paper Co-Authored by Netflix CEO R...
by eschneider on Tuesday December 06, 2022 @01:08PM
(#33884472)
Late 90s/early 2000s. I definitely spent some time with the licensing code and I know it definitely did nothing like that then.
Re:Memory Leaks Detection Paper Co-Authored by Netflix CEO R...
by neilv on Wednesday December 07, 2022 @01:21PM
(#33897993)
My experience must've been a little before that (I left that job in the mid-90s).
I could be mistaken. Or maybe the licensing code changed (due the Web explosion, or to evolution of a great product, or some other reason).
(I think Purify might've been the first phoning-home tool I saw, finding a way to email Pure if you exceeded your simultaneous licenses, but I might've misunderstood at the time. Around that time, it was normal for big-ticket Unix workstation software to have network license managers, which were tied with stale NFS mounts at our site as the most common cause of a fleet of expensive engineers on expensive workstations with expensive software all suddenly unable to work. :) )
A related awesome C development tool we used for discovering memory errors before then was the Saber-C debugger. https://www.softwarepreservation.org/projects/interactive_c/...