#1204 Test fCmd-9.4 relies on buggy rename implementation

obsolete: 8.0.3
open-postponed
1
2013-03-24
2000-10-26
Anonymous
No

OriginalBugID: 1399 Bug
Version: 8.0.3
SubmitDate: '1999-03-02'
LastModified: '2000-04-03'
Severity: LOW
Status: Assigned
Submitter: pat
ChangedBy: hobbs
OS: Linux-SuSE
OSVersion: + NCR Unix + Siemens Reliant Unix
Machine: Other
FixedDate: '2000-10-25'
ClosedDate: '2000-10-25'

Name:
Ulrich Schöbel

ReproducibleScript:
Test fCmd-9.4 works on Linux and NCR, but fails on Siemens (Reliant 5.43).

ObservedBehavior:
file rename uses the rename syscall. According to the man page and an ancient
AT&T spec "rename" should fail with EACCES when moving a 555 directory to a new
destination. fCmd-9.4 expects a buggy implementation of "rename".

DesiredBehavior:
Thus, Tcls "file rename" should fail, too.

The solaris docs seem to say the same thing, but it does indeed
work without error on Solaris (as well as Linux and HP)...
-- 04/03/2000 hobbs

Discussion

  • Andreas Kupries

    Andreas Kupries - 2001-08-23
    • assigned_to: nobody --> vincentdarley
     
  • Vince Darley

    Vince Darley - 2001-09-17
    • priority: 5 --> 1
    • status: open --> open-postponed
     
  • Vince Darley

    Vince Darley - 2002-04-04
    • assigned_to: vincentdarley --> nobody
     
  • Vince Darley

    Vince Darley - 2002-04-04

    Logged In: YES
    user_id=32170

    This is not something I am qualified to look into.

     
  • Don Porter

    Don Porter - 2002-07-05

    Logged In: YES
    user_id=80530

    should this be closed as really being "bugs"
    in the operating system(s) ?

     
  • Don Porter

    Don Porter - 2003-11-12
    • assigned_to: nobody --> vincentdarley
     
  • Vince Darley

    Vince Darley - 2003-11-12
    • assigned_to: vincentdarley --> hobbs
     
  • Mike Small

    Mike Small - 2008-02-11

    Logged In: YES
    user_id=691174
    Originator: NO

    OpenBSD 4.2-current also fails on this test when using Tcl 8.5.1.

    According to this page below, an implementation has the option to fail
    when the source directory to rename lacks write permission:

    http://www.opengroup.org/onlinepubs/009695399/functions/rename.html

    "Write access permission is required for the directory containing
    old and the directory containing new. If the old argument points
    to the pathname of a directory, write access permission may be
    required for the directory named by old, and, if it exists, the
    directory named by new."

     
  • Don Porter

    Don Porter - 2013-03-24
    • assigned_to: hobbs --> stwo
     
  • Don Porter

    Don Porter - 2013-03-24

    What's the story on BSD systems now?

     
  • Mike Small

    Mike Small - 2013-05-07

    Using 8.6.0, it still fails for me on openbsd-current dated May 3,
    2013 on macppc:

    fCmd.test

    ==== fCmd-9.4.b file rename: comprehensive: dir to new name FAILED
    ==== Contents of test case:

    file mkdir td1 td2
    testchmod 555 td2
    file rename td1 td3
    file rename td2 td4
    list [lsort [glob td*]] [file writable td3] [file writable td4]

    ---- Test generated error; Return code was: 1
    ---- Return code should have been one of: 0 2
    ---- errorInfo: error renaming "td2" to "td4": permission denied
    while executing
    "file rename td2 td4"
    ("uplevel" body line 5)
    invoked from within
    "uplevel 1 $script"
    ---- errorCode: POSIX EACCES {permission denied}
    ==== fCmd-9.4.b FAILED

    I tried NetBSD 6.0.1 and DragonFlyBSD 3.3 and it passed in both of those.

    Now that I read my comment below, I'm not sure how I thought that
    quote applied here. Maybe I missed the word _containing_? Sorry about
    that. I wear glasses now.

     
  • Mike Small

    Mike Small - 2013-05-08

    I was hasty with the last paragraph of this new comment. Of course it was the second sentence of the quote, with the words "write access permission may be required for the directory named by old" that applies here. The younger me wasn't as blind as I thought.

     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks