> > I'll try to look into this. What's puzzling is that we get tested on >> *many* Linux boxes but the overwhelming majority report no problem here.
> something to do with svk being on the box but never having been run by that user? > istr something like this before. iirc hitting <enter> will make the problem go away, never to return, because svk is waiting for input. Yeah, but svk is waiting for a 'y' or 'n', to set up the default cache dir. Seems to be as much an svk issue, as svk info shouldn't have to create that user's svk environment by default. Or, at least, a switch to allow svk --dont_init info a ------------------- Andy Bach Systems Mangler Internet: [EMAIL PROTECTED] Voice: (608) 261-5738 Fax: 264-5932 "It's true that I've driven through a number of red lights. But on the other hand, I've stopped at a lot of green ones I've never gotten credit for" Glen Gould
