Messages in this thread | | | Date | Fri, 14 Sep 2007 11:07:37 +0200 (CEST) | From | Bodo Eggert <> | Subject | Re: O_NOLINK for open() |
| |
On Thu, 13 Sep 2007, Jan Kara wrote:
> > > However, it occurs to me that this problem goes away if there were > > > a method create a file in an unlinked state to begin with. However > > > there does not appear to be any such mechanism in Linux's open() > > > interface. > > > > Having no window for creating stale temp files is nice to have. We only > > need a clever fool to implement it.-) But since it's hard to get killed > > just in the right moment for having a stale temp file, there is very low > > interest for this feature.
> I don't think this is a problem. The file is simply created with link > count 0. As soon as the process closes the file, it gets deleted. So > there would be no stale files... Or did you mean anything else?
This feature does, AFAIK, not yet exist. Therefore we'd need a code monkey. -- Top 100 things you don't want the sysadmin to say: 42. Hey Fred, did you save that posting about restoring filesystems with vi and a toothpick? More importantly, did you print it out? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |