Shell Programming and Scripting

Originally Posted by dheian

No, nginx. Apparently the sed changing ownership issue can be fixes by adding the -c switch to the sed command.

Originally Posted by ygemici

I understood you..But sed doesnt change ownerships..I think your webserver isnt recognizes your web page files because of its changed modif times.

For example

Code:

ls -l filex
-rw-rw-r-- 1 testuser testuser 44 Mar 27 08:29 filex
 
whoami
root
 
sed -i '2i selam' filex  # in edit mode (changes date)
-rw-rw-r-- 1 testuser testuser 50 Mar 27 08:32 filex
 
sed -ci '2i selam' filex   # in copy mode (changes date)
ls -l filex
-rw-rw-r-- 1 testuser testuser 56 Mar 27 08:33 filex

I use GNU sed version 4.1.5

Originally Posted by ygemici

I think your webserver isnt recognizes your web page files because of its changed modif times.
...snip...
Your problem is webserver doesnt recozgnize because of your file's timestamps changes..
I think you must use touch command for update modif times of your files.

add your command

Code:

find . -type f -print0 | xargs -0 touch -ma

Originally Posted by alister

I believe that to be a misleading example, because you're running as root and root can chown the files it creates to preserve ownership. If sed is run as a regular user who has read access to the files but is not the owner, then it could not possibly maintain ownership unless it is running suid root.

Even when running with superuser privileges, at least some implementations out there do not even attempt to preserve ownership. The following example is using an old version of freebsd sed on osx 10.4.11.

Code:

$ whoami
testuser
$ touch myfile
$ ls -l myfile
-rw-r--r--   1 testuser  testuser  0 Apr 10 10:38 myfile
$ sudo su
Password:
# whoami
root
# sed -i '' 'i\           
> hi' myfile
# ls -l myfile
-rw-r--r--   1 root  testuser  0 Apr 10 10:41 myfile
#

Looking at current freebsd sed source, http://www.freebsd.org/cgi/cvsweb.cg...?annotate=1.44, these days it seems to make an attempt to preserve ownership and permissions:

Code:

                    389:                        fchown(fileno(outfile), sb.st_uid, sb.st_gid);
                    390:                        fchmod(fileno(outfile), sb.st_mode & ALLPERMS);

Again, as mentioned above, even though the attempt is made, fchown cannot change the ownership of "outfile" unless it's run with superuser priviliges.




That doesn't make any sense to me. If a webserver ceased to serve a file because of a change in the file's timestamps, it would be impossible to edit/update a file on a website without further intervention. If I'm mistaken, I'd appreciate some elaboration or a link to further information on the matter.

Regards,
Alister

Originally Posted by ygemici

I can try different sed on freebsd or solaris and old system if i can find any chance..I work on GNU sed 4.1.5..ok