We have an installation that we deploy to a bunch of workstations. We prefer
if the installation uses the temporary file directory that Windows has already
allocated for the user.
The entry for /tmp in /etc/fstab, or the directory /tmp, is preferred.
If neither is found, the patch mounts /tmp at t
On 08/09/2010 3:41 PM, Christopher Faylor wrote:
> Thanks for the patch but I don't think this is generally useful. If you
> need to mount /tmp somewhere else then it should be fairly trivial to
> automatically update /etc/fstab. Corinna may disagree, but I think we
> should keep the parsing of /
On 09/09/2010 12:50 AM, Corinna Vinschen wrote:
> Apart from changing /etc/fstab or /etc/fstab.d/$USER by some installer
> script, why not just add a one-liner profile script along the lines of
>
> /etc/profile.d/tmp-mnt.sh:
>
>mount -f `cygpath -m "${TEMP}"` /tmp
That's a pretty good idea.
On 09/09/2010 1:03 PM, Dave Korn wrote:
>> but I think we
>> should keep the parsing of /etc/fstab as lean as possible;
>
> I don't understand why. How many times per second does /etc/fstab get
> parsed?
I interpreted cgf's comment as not wishing to add to the amount of coupling
with /etc/fs
On 09/09/2010 2:16 PM, Pierre A. Humblet wrote:
> So, for example, if the user logs in interactively while a cron job (or
> another service)
> is running, /tmp may be mapped differently than if no cron job is running,
> because
> TMP may be defined differently in the service environment.
> That i
The current implementation of rexec() uses fstat() and it seems
to pick up the wrong values for st_mode. As a consequence
the code keeps complaining about the permissions for ~/.netrc
and won't complete successfully.
I don't know enough about the how the re-mapping of stat/stat64
works within cyg
