Re: [WebDNA] sudo and shell
This WebDNA talk-list message is from 2010
It keeps the original formatting.
numero = 105161
interpreted = N
texte = Thierry Almy wrote:[snip]> this looks quite tricky ... more difficult that I have thought ...> > I changed the ownership of the Content Folder to 777 -R, but it didn't > help, guess I'd have to change the folders above as well ...> > I don't want to mess up permissions in the PodcastProducer Library, it's > quite a delicately system and I don't want to break it! so I went back > to 775.You won't have to change perms a level above the 'Content' folder, but you will have to change the actual file that you want to delete. Boththe content and the file to delete must be writable by WebDNA's useror group.Also, it shouldn't hurt the PodcastProducer setup in going the directionof "more accessible" regarding permissions. 777 should be fine.. at least for testing.> If the rm -rf isn't possible, I'm thinking about writing the folder > paths to be deleted in a database. > Then retrieve them all together formatted as a shell script which can be > copy/pasted in to the terminal then enter the password manually.> > It's not the solution that I have dreamed of but better than nothing ...Sure, access to the non Web portions of a server via an appropriate SSH session is likely more recommended. There is a reason why you run your web environment as a different user:group thanthe rest of the server. ;-)Donovan-- Donovan BrookeEuca Design Center[Practical-Ethical-Efficient]www.euca.usegg.bzartglass-forum.com
Associated Messages, from the most recent to the oldest:
Thierry Almy wrote:[snip]> this looks quite tricky ... more difficult that I have thought ...> > I changed the ownership of the Content Folder to 777 -R, but it didn't > help, guess I'd have to change the folders above as well ...> > I don't want to mess up permissions in the PodcastProducer Library, it's > quite a delicately system and I don't want to break it! so I went back > to 775.You won't have to change perms a level above the 'Content' folder, but you will have to change the actual file that you want to delete. Boththe content and the file to delete must be writable by WebDNA's useror group.Also, it shouldn't hurt the PodcastProducer setup in going the directionof "more accessible" regarding permissions. 777 should be fine.. at least for testing.> If the rm -rf isn't possible, I'm thinking about writing the folder > paths to be deleted in a database. > Then retrieve them all together formatted as a shell script which can be > copy/pasted in to the terminal then enter the password manually.> > It's not the solution that I have dreamed of but better than nothing ...Sure, access to the non Web portions of a server via an appropriate SSH session is likely more recommended. There is a reason why you run your web environment as a different user:group thanthe rest of the server. ;-)Donovan-- Donovan BrookeEuca Design Center[Practical-Ethical-Efficient]www.euca.usegg.bzartglass-forum.com
Donovan Brooke
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:
Re(2): MASTER_STORE revision (2002)
WebDNA vars parsed in FLASH (ActionScript) (2004)
blank page from template (1997)
Logging purchases (1997)
Re:2nd WebCatalog2 Feature Request (1996)
WebCat for mass emailings (1997)
Quick Question (1997)
Authenticate (1997)
problems with 2 tags shakur (1997)
Sample Tearoom Search Error (1997)
search across ip/domain addresses? (1998)
RequiredFields template (1997)
Status of variable hierarchy changes? (2000)
WebCatalog NT beta 18 problem (1997)
Dummy Credit Card Number for debug? (1997)
PSC recommends what date format yr 2000??? (1997)
[WebDNA] two ideas for running a cluster of WebDNA servers (2019)
[LOOP]/[BREAK] bug (2000)
Search/sort in URL Was: GuestBook example (1997)
OT: Javascript Jump Menu (2004)