Re: WebSTAR, OSX, WebDNA permissions problem ...

This WebDNA talk-list message is from

2005


It keeps the original formatting.
numero = 61410
interpreted = N
texte = As everyone is indicating, the problem is likely an ownership and permissions issue. Here's how I'd go about it on my Linux box. You will need to adjust for WebStar in place of apache. Funny thing is I'm really a diehard Mac user, but I only know how to use Linux/Apache at the commandline. Here's what NOT to do: >chmod -r 777 folder While that will fix your problem, anyone can make, change or execute anything in the folder. The real solution is to: 1. Determine what process is writing the files, i.e. who needs permission? >ps -aux Look for the web server process running. On my Linux box it is httpd and the owner is apache. This tells me that apache should own the folder it is writing to regularly. 2. Determine who owns the folder of interest. >cd "the parent of the directory that apache will write to" I used quotes because Mac users often use spaces. Then, >ls -al Look for the directory that apache will be writing to. Then check its ownership and permissions. It should be apache:apache for owner:group and the permissions may be 664 or rw-rw-r--. That is fairly safe, but 660 is better if anyone else can access the box but an administrator and you have some confidential information there. You may have to >su or >sudo with an admin password to make the following change: >chown -r apache:apache "the directory that apache will write to" >chmod -r 664 "the directory that apache will write to" Then, gracefully restart apache and WebCatalog using the scripts that are provided in the sbin folder (su or sudo required for the following commands): >/etc/sbin/apachectl -k graceful >/etc/sbin/WebCatalogCtl restart If you have trouble locating the scripts, try >locate apachectl (or its WebStar equivalent) >locate WebCatalogCtl The scripts are recommended over killing the process because they finish running existing processes before restarting. That's the step by step that I recall for my Linux box ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: WebSTAR, OSX, WebDNA permissions problem ... ( devaulw@onebox.com 2005)
  2. Re: WebSTAR, OSX, WebDNA permissions problem ... ( devaulw@onebox.com 2005)
  3. Re: WebSTAR, OSX, WebDNA permissions problem ... ( John Peacock 2005)
  4. Re: WebSTAR, OSX, WebDNA permissions problem ... ( "Nitai @ ComputerOil" 2005)
  5. Re: WebSTAR, OSX, WebDNA permissions problem ... ( Jesse Proudman 2005)
  6. Re: WebSTAR, OSX, WebDNA permissions problem ... ( "Nitai @ ComputerOil" 2005)
  7. Re: WebSTAR, OSX, WebDNA permissions problem ... ( Jesse Proudman 2005)
  8. Re: WebSTAR, OSX, WebDNA permissions problem ... ( "Nitai @ ComputerOil" 2005)
  9. Re: WebSTAR, OSX, WebDNA permissions problem ... ( charles kline 2005)
  10. WebSTAR, OSX, WebDNA permissions problem ... ( Kenneth Grome 2005)
As everyone is indicating, the problem is likely an ownership and permissions issue. Here's how I'd go about it on my Linux box. You will need to adjust for WebStar in place of apache. Funny thing is I'm really a diehard Mac user, but I only know how to use Linux/Apache at the commandline. Here's what NOT to do: >chmod -r 777 folder While that will fix your problem, anyone can make, change or execute anything in the folder. The real solution is to: 1. Determine what process is writing the files, i.e. who needs permission? >ps -aux Look for the web server process running. On my Linux box it is httpd and the owner is apache. This tells me that apache should own the folder it is writing to regularly. 2. Determine who owns the folder of interest. >cd "the parent of the directory that apache will write to" I used quotes because Mac users often use spaces. Then, >ls -al Look for the directory that apache will be writing to. Then check its ownership and permissions. It should be apache:apache for owner:group and the permissions may be 664 or rw-rw-r--. That is fairly safe, but 660 is better if anyone else can access the box but an administrator and you have some confidential information there. You may have to >su or >sudo with an admin password to make the following change: >chown -r apache:apache "the directory that apache will write to" >chmod -r 664 "the directory that apache will write to" Then, gracefully restart apache and WebCatalog using the scripts that are provided in the sbin folder (su or sudo required for the following commands): >/etc/sbin/apachectl -k graceful >/etc/sbin/WebCatalogCtl restart If you have trouble locating the scripts, try >locate apachectl (or its WebStar equivalent) >locate WebCatalogCtl The scripts are recommended over killing the process because they finish running existing processes before restarting. That's the step by step that I recall for my Linux box ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ devaulw@onebox.com

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: strip .0 off off IPaddress (1999) Ampersands in database fields? (1998) Server IP address? (1998) WebCatalog can't find database (1997) multiple record replace (2001) Cookies (1999) Nested tags count question (1997) Sku numbers (1997) [Reload mydata.db] (1998) Removing a character (2000) Need help with emailer- 2 issues (1997) sorting and summarizing (1998) more [sendmail] woes.. (2000) SmithMicro Help! -- Can't access WebCatalog Admin! (2001) Mixing and/or in searches (1998) How to Display text in empty fields (1997) ooops...WebCatalog [FoundItems] Problem - LONG - (1997) Emailer [cart] file names (1997) Quickie question on the email templates (1997) Almost a there but..bye bye NetCloak (1997)