Recently I've been trying to use debug tools to understand what happens to a software tool that is invoked by tup. But the .tup/mnt/@tupjob-#/ directories have been impenetrable.
In fuse_fs.c I've disabled the pgid check so that other process groups should be able to access the fuse directories in the same way the tup-launched software tool accesses those directories. However, I'm not able to see or access anything under .tup/mnt/ from other contexts. I'm certain that the directories exist because a build tool that prints pwd or navigates around the fuse file system does have apparently normal access to the whole fuse directory tree. Why is it that other tools, not launched by tup, cannot even detect the existence of the directories under .tup/mnt/? Thanks for any hints, Lee Winter Nashua, New Hampshire United States of America -- -- tup-users mailing list email: [email protected] unsubscribe: [email protected] options: http://groups.google.com/group/tup-users?hl=en --- You received this message because you are subscribed to the Google Groups "tup-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
