Hi, sorry for the late reply... > > > > I can install a fresh machine with an old version, > following our update > > path here and see if the problem surfaces again. But this > will be after > > the weekend. > > Please let me know how it goes. I am totally confused by this repotr, > as I have never seen that very simple block of code blow up. Is there > anything strange about the shell on that system (i.e., is it > posh or ksh > or something)? There may be a lurking XSI'ism blowing up, but that's > all I can think of.
The shell is bash 3.0. I just tried reproducing the effect with a clean reinstall, but what I reported earlier didn't happen. So either it's a Heisenbug, or I did something to the config files earlier that made it happen - though I have no idea what that would be. Feel free to close the bug. I'll keep an eye open in the future for a similar situation and if it happens, I'll try to find out exactly what happens in the setup scripts. Regs, Sven