lkml.org 
[lkml]   [2008]   [Mar]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
Subjectunexpected rename() behaviour
Hi,

The following behaviour was unexpected (tested on Debian/ext3):

$ echo 1 > 1
$ ln 1 2
$ cat 2
1
$ ./rename 2 1
$ echo $?
0
$ cat 2
1

The code for ./rename is simple:

---
/* compile: gcc -o rename rename.c */
#include <stdio.h>
int main(int argc, char *argv[]) { return rename(argv[1], argv[2]); }
---

I thought this must be wrong behaviour, but I have been unable to
confirm what the correct result should be in this special case. rename()
returns success, but the source file is intact, which seems odd. The
"mv" command specifically checks for cases like this and calls
unlink("2") instead of rename("2", "1"). Are all applications meant to
do this? What standards describe what rename() should do in cases like this?

Regards,
Ketil Froyn


\
 
 \ /
  Last update: 2008-03-29 01:11    [W:0.051 / U:0.364 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site