4 ms·
I read this, but seemed to skip over the part where he explains why this changed suddenly, when the behavior was documented? What changed to make the perl beco
by davidu 10y ago
I read this, but seemed to skip over the part where he explains why this changed suddenly, when the behavior was documented?
What changed to make the perl become capable whereas previously it lacked the low port capability?
- lmz 10y agoThat seems to be a site-specific configuration.
- ars 10y agoHe usually started emacs directly. In this case he started emacs via a perl command, very very indirectly. Also, a recent change was an admin setting TMPDIR, previously it had been left unset. So it was a combination of two things that triggered it, and not one alone.
- raarts 10y ago> So it was a combination of two things that triggered it, not one alone And this basically sums up all the troubleshooting time sinks I've experienced in my career.
- mjd 10y agoThat is a good point. I still don't know the answer to that! I _think_ it's that the sysadmins added the new capability to Perl sometime in the last few weeks, and the the problem then didn't appear until after the next time I reloaded the system configuration. I will confirm this with the sysadmins and add it to the article. Thanks!
- mjd 10y agoI checked with Frew on this, and we still don't know the answer.