From: rr.rosas@...
Date: 2014-05-19T11:15:20+00:00
Subject: [ruby-core:62673] [ruby-trunk - Bug #9850] [Open] FileUtils.mv shouldn't try to make sure the owner is preserved

Issue #9850 has been reported by Rodrigo Rosenfeld Rosas.

----------------------------------------
Bug #9850: FileUtils.mv shouldn't try to make sure the owner is preserved
https://bugs.ruby-lang.org/issues/9850

* Author: Rodrigo Rosenfeld Rosas
* Status: Open
* Priority: Normal
* Assignee: 
* Category: lib
* Target version: 
* ruby -v: ruby 2.1.2p95 (2014-05-08 revision 45877) [x86_64-linux]
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
I found an issue with one of our servers due to user ids not being mapped correctly between the NFS server and client. In the NFS server side there was a settings to consider anonymous users as an specific user and that worked fine for a while.

When we came with a different implementation that writes documents to a temp dir, process them and move to the target directory I found that it wouldn't work on the server for which the owner of the mounted NFS export was set to nobody.

I consider this a bug because running "mv" on the Linux server wouldn't trigger any errors but FileUtils.mv will try to "chown" after moving the file and I don't think it should do anything different from simply moving the file.

I had to spend some time fixing the user id mapping on that server to fix the problem but I thought it would be a good thing to do to report this issue since this may be considered a bug of FileUtils.mv.



-- 
https://bugs.ruby-lang.org/