From: David Mitchell <mitchell@uc...> - 2001-04-16 20:07:02
I'm not subscribed to the list, but I checked the archives and
this didn't seem to be addressed. If you specify the --isodir
option with a path beginning with ., the function
ConfigureLogsAndTmp get confused. Specifially, when it sets
$procno using `cut -d'.'`, the results are not what is expected.
The result is that the new tmp directory gets promptly blown
away, and things go quickly downhill.
I'm not sure if the best method to fix this is to set $procno via
some other means, or just not allow '.' at the beginning of
paths. I found this when I tried to do "--isodir ./isos", which
seems like a reasonable thing to do.