On Sat, March 19, 2011 3:01 pm, Ron Wilson wrote:
> Prefixing a command
> with a variable assignment causes the command shell to export that
> variable for the duration of the command
(Amazing how few people seem to know that :-) )
> (unless your version of cron
> uses a limited version of the
On Fri, Mar 18, 2011 at 12:12 PM, John Found wrote:
> For me "least astonishment" means simply: If the file is changed by VCS,
> then later, VCS must knows about this fact and must take it into account.
> If the user changed the file by any other way (edit, copy paste, etc.) VCS
> should
> consid
On Fri, Mar 18, 2011 at 12:12 PM, John Found wrote:
> I have very little experience with any version control systems.
> For me "least astonishment" means simply: If the file is changed by VCS,
> then later, VCS must knows about this fact and must take it into account.
> If the user changed the fil
On Sat, Mar 19, 2011 at 6:49 AM, Eric wrote:
> HOME is just an environment variable, so if you could find some way to set
> it to some other location just before Fossil runs ...
>
> (a wrapper for fossil, perhaps)
I had forgotten that.
Depending on your version of cron, this command should work:
On Sat, March 19, 2011 12:29 am, Nolan Darilek wrote:
> Thanks. It isn't that I couldn't figure out a convoluted solution
> involving multiple users, groups and permissions. I just thought that
> Fossil could gracefully degrade if it couldn't write to the home
> directory, not enabling some functi
5 matches
Mail list logo
