[WebDNA] Permission Settings
This WebDNA talk-list message is from 2009
It keeps the original formatting.
numero = 102740
interpreted = N
texte = > So, one way for Ken to perhaps fix his issue is to set > the umask to the desired octal complement: > > umask 002 Actually I changed my /etc/profile umask entry to 002 when I setup the server last month, so the problem I posted here the other day came about long after this change had already been made. In other words, you had a good thought here Donovan, and if I had not already done this I would certainly try it. But since it didn't work for me it may not help others much either, at least on Ubuntu since that's the OS I'm running WebDNA on right now. I can probably use a shell script to fix this problem if it ever becomes a major issue. But I was really shocked to learn that even after setting the permissions I wanted in my WebCatalog Prefs file, WebDNA was apparently ignoring those permissions! ----------------------------------------- My guess is that it must be the way WebDNA invokes the OS that allows the original permissions to be changed when files are moved or copied ... Perhaps WebDNA tells the OS to write a blank file to the new location and the OS creates this file using its own default permissions. Then WebDNA tells the OS to append the contents of the old file to the new blank file, and since this does not change the permissions of the new file they remain set to the OS defaults. This may not be what's actually going on, but it certainly explains why the new file uses the OS default permissions rather than using WebDNA's file permissions. ----------------------------------- I think most people actually need and/or expect WebDNA to "leave the file permissions alone" when it copies and/or moves files. If this is true it will probably be worth your effort (some day when you have the time) to modify WebDNA's internal code so that it actually fixes these file permissions after it has copied or moved files. Then again, if I'm the only one who wants the permissions to remain the same after a file is copied or moved, it wouldn't make much sense to bother with this, would it? ----------------------------------- Thanks for thinking about this a little more and suggesting possible solutions Donovan, I really appreciate it. :) Sincerely, Ken Grome
Associated Messages, from the most recent to the oldest:
> So, one way for Ken to perhaps fix his issue is to set > the umask to the desired octal complement: > > umask 002 Actually I changed my /etc/profile umask entry to 002 when I setup the server last month, so the problem I posted here the other day came about long after this change had already been made. In other words, you had a good thought here Donovan, and if I had not already done this I would certainly try it. But since it didn't work for me it may not help others much either, at least on Ubuntu since that's the OS I'm running WebDNA on right now. I can probably use a shell script to fix this problem if it ever becomes a major issue. But I was really shocked to learn that even after setting the permissions I wanted in my WebCatalog Prefs file, WebDNA was apparently ignoring those permissions! ----------------------------------------- My guess is that it must be the way WebDNA invokes the OS that allows the original permissions to be changed when files are moved or copied ... Perhaps WebDNA tells the OS to write a blank file to the new location and the OS creates this file using its own default permissions. Then WebDNA tells the OS to append the contents of the old file to the new blank file, and since this does not change the permissions of the new file they remain set to the OS defaults. This may not be what's actually going on, but it certainly explains why the new file uses the OS default permissions rather than using WebDNA's file permissions. ----------------------------------- I think most people actually need and/or expect WebDNA to "leave the file permissions alone" when it copies and/or moves files. If this is true it will probably be worth your effort (some day when you have the time) to modify WebDNA's internal code so that it actually fixes these file permissions after it has copied or moved files. Then again, if I'm the only one who wants the permissions to remain the same after a file is copied or moved, it wouldn't make much sense to bother with this, would it? ----------------------------------- Thanks for thinking about this a little more and suggesting possible solutions Donovan, I really appreciate it. :) Sincerely, Ken Grome
Kenneth Grome
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
syntax question, not in online refernce (1997)
FEA REQ: One .hdr, multiple .db's (2003)
using showpage and showcart commands (1996)
Group search doesn't work. (1997)
Web Catalog Instability (2000)
Secure server question (1997)
WebCat2b13MacPlugIn - [showif][search][/showif] (1997)
& in Lookups (1997)
Sendmail truncation in Eudora Clients (1998)
[TaxableTotal] - not working with AOL and IE (1997)
[BULK] [WebDNA] [BULK] Mac OS X LION has no FastCGI (2011)
Error.html (1997)
Freeze (2003)
[LISTFILES] (1998)
Moment of Thanks (1997)
Image Upload and Auto Resize? (2003)
Calendar using WebCatalog? (1997)
serial number not working (1998)
cybercash (2002)
[HIDEIF] inside [FOUNDITEM] (1997)