Hi,

Javier Fernández-Sanguino Peña:
> > The interesting part about this is that one cannot change the work
> > directory in the rc file either, because the temporary file for sourcing
> > the configuration is stored in ... surprise ... the work directory.
> 
> That's does not seem to be true, based on how I read the code, the
> preprocessing is done in the work directory, but it's done in every tiger
> run. If you modify the RC file, then the preprocessed rc file will also be
> modified.
> 
Exactly -- the preprocessing is done in the work directory. But if the
work directory doesn't exist in the first place ...

> > So there's no way to change the work directory without modifying the
> > package (or one of its read-only files). I'd consider that to be a bug.
> 
> Which read-only file? You can use the '-w' switch to change the working
> directory for tiger in any run. It defaults to 'run/' (relative path) so that
> people running the package (in other OSes) do not need to have it installed.
> 
You can't pass -w to /usr/sbin/tigercron.

> > Fix: use $(tempfile) for the above file name.
> 
> That fix is not useful. Tempfile is not available in all the different
> systems that Tiger can run on.
> 
mktemp, then? I'm not that familiar with different flavors of
which-utility-is-available-where.

-- 
Matthias Urlichs   |   {M:U} IT Design @ m-u-it.de   |  [EMAIL PROTECTED]

Attachment: signature.asc
Description: Digital signature

Reply via email to