Sponsored Content
Special Forums UNIX Desktop Questions & Answers Web Server/Permissions issues. Post 302890157 by LightCastle on Tuesday 25th of February 2014 11:58:36 AM
Old 02-25-2014
Web Server/Permissions issues.

I do not know if this is the correct place to post this, and I have tried to trawl through relevant articles to fix the issue, but I am stumped.

I have a server, log as root.

var/www is root:root

var/www/website-one is root:root

var/www/website-one/neosmart-stream is root:root

This error pops up

It is not possible to create new directories via PHP mkdir(). /var/www/website-one/neosmart-stream/ (CHMOD 0775) is not writeable.
Try to set your webserver as owner of /var/www/website-one/neosmart-stream/

Has this web server been setup incorrectly ?

On another web server not managed by me the permissions/group are right and everything works fine ?

Can anyone direct me on the right path please ?
 

5 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Permissions issues

I'm hoping this is a pretty simple question. I have a problem were memebers of a group can't delete or overwrite a file. The box is setup several users all part of the same group. Now default umask is 002. The problem I run into is there are processes that add to, del, and over write files. ... (3 Replies)
Discussion started by: lightspd
3 Replies

2. UNIX for Dummies Questions & Answers

Permissions Issues FTP server

Hi all, Quick question, im going to find this a bit hard to explain but ill give it a go. Basically i have an admin account on an FTP server that i want to be able to control ALL files without having to use sudo (as i need to run cron scripts to move files that are owned by a number of... (2 Replies)
Discussion started by: mokachoka
2 Replies

3. OS X (Apple)

Wordpress & Git, urgent permissions issues, need help...

Heya, So I recently upgraded my MacBook to a solid state drive, during the re-install of Snow Leopard I chose to abandon MAMP and use the built in Apache & PHP and in doing so moved my ~/Sites to /Library/WebServer/Documents from a Time Machine backup. During this transition the permissions... (0 Replies)
Discussion started by: s3w47m88
0 Replies

4. OS X (Apple)

TextMate web server permissions

this could be a dumb question. i am still becoming used to usr / group permissions. permissions to place a file into XAMPP/htdocs. the problem is that when i go to place a TextMate file into XAMPP/htdocs a window comes up and states: Type your password to allow TextMate to make changes. ... (2 Replies)
Discussion started by: cowLips
2 Replies

5. Solaris

Permissions configuration for web server

Greetings! I have a Solaris workstation that I use for web hosting. It runs SAMP and everything was working good for me until I got a need to add a couple of co-workers to help me with development. I'm trying to find some guidance for how to set up filesystem permissions so everybody would be... (3 Replies)
Discussion started by: pn8830
3 Replies
PROOFD(1)						      General Commands Manual							 PROOFD(1)

NAME
proofd - PROOF (The Parallel ROOT Facility) DESCRIPTION
Using PROOF (The Parallel ROOT Facility) one can analyze trees in parallel on a cluster of computers. The PROOF system consists of the proofd(1) from-end program which is started via inetd(8). proofd takes care of user authentication and overlays itself then with the desired version of the proofserv(1) executable. The proofserv(1) is a basically the same as the ROOT interactive module root(1), except that it reads its commands from a socket instead of from the terminal. Since it is a remote server it will not do graphics and therefore is not linked with any graphics libraries (Motif, X11, etc.). SETTING UP PROOF
Since you need to handle sensitive system files, you need to have root (the user, not the program!) privileges. Also, it's recommended that you read the appropriate man(1) pages first. These are inetd(8) (the internet daemon), sysklogd(8) and syslog(3) (the system logger dae- mon), and init(8) (the SYSV process control initializer). In other words: Be very VERY carefull when installing proofd There, I said it. And ofcourse, no warrenties what so ever. 1 Make sure every node has ROOT installed. We'll assume you installed the ROOT applications in <bindir> (e.g. /usr/bin) and the PROOF configuration files in files in <proofdir>/etc (e.g. /usr/share/root/etc). 2 The TCP port 1094 was allocated by IANA, ( www.iana.org <Iwww.iana.org> ), to rootd, so add to /etc/services the lines: proofd 1093/tcp rootd 1094/tcp 3 On each node, add to /etc/inetd.conf the lines: proofd stream tcp nowait root <bindir>/proofd proofd <proofdir>/proof rootd stream tcp nowait root <bindir>/rootd rootd -i You can substitute the <proofdir> with any directory that holds your PROOF configuration, for example /etc/root/proof. However, it should be shared among all nodes in the cluster. 4 Restart inetd or force it to re-read the config file: kill -1 <inetd pid> If you use SYSV init(8) scripts, you can probaly just do /etc/init.d/inetd restart or whatever is appropriate for your system. 5 On the master node, add to /etc/syslog.conf the line: local5,local6.debug <proofdir>/log/proof.log and all slave nodes: local5,local6.debug @<master hostname> where <master hostname> is domain name of the master node. All PROOF syslog messages will be collected on the master node. Just make one node in the cluster the master, all others are slaves. 6 On all nodes, change the below lines in /etc/syslog.conf, *.info;mail.none;news.none;authpriv.none /var/log/messages to: *.info;local5,local6,mail.none;news.none;authpriv.none /var/log/messages 7 Create an empty <proofdir>/log/proof.log: echo "" > <proofdir>/log/proof.log 8 Restart syslogd or force it to re-read the config file: kill -1 <syslogd pid>. If you use SYSV init(8) scripts, you can probaly just do /etc/init.d/sysklogd restart or whatever is appropriate for your system. 9 Edit <proofdir>/etc/proof.conf to reflect your cluster configuration. See the example proof.conf file for more information. If you installed ROOT using some precompiled package (for example a Redhat Linux or a Debian GNU/Linux package), steps 2 to 4 may already be done for you. If you're running Linux, Steps 5 to 7 can be somewhat automated using the script proof-facility in <proofdir> of your distribution. This script uses syslog-facility(1), from the Linux syslog(1) distribution, and may run on other platforms as well - but no warrenties mind you! Step 9 is completely up to the user. EXAMPLE
That's it. To test PROOF try the following: root [1] gROOT->Proof("<master hostname>") root [2] gPROOF->Print() <shows information on the master and all active slave servers> root [3] .q FILES
<proofdir> The location of your PROOF data. In binary packages, like for Redhat LinuxI or Debian GNU/Linux, this will probably be /usr/share/root/proof. If you got a binary tar(1)-ball from the ROOT website, or a build it yourself without the static paths option, then this directory could be ROOTSYS/proof. However, you may set it to something else when starting your server. <proofdir>/etc This directory holds all the configuration files for your cluster(s). <proofdir>/etc/<cluster>.conf This is the cluster named <cluster> configuration file. See <proofdir>/etc/<cluster>.conf.sample for an example. <proofdir>/etc/motd This is Message-Of-The-Day file. See <proofdir>/etc/motd.sample for an example. <proofdir>/etc/noproof If this file is present, all PROOF services will be diabled. See <proofdir>/etc/noproof.sample for an example. <proofdir>/etc/proof.conf This is the PROOF configuration file. See <proofdir>/etc/proof.conf.sample for an example. ~/.rootnetrc.conf Configuration file for network access. Here you specify login names and pass word, so it MUST be read/write-able only by the user. See <proofdir>/etc/rootnetrc.conf.sample for an example. <proofdir>/log This directory holds the log files from the master and slaves. <proofdir>/log/proof.log Syslog(1) log file for PROOF. SEE ALSO
proofserv(1) , root(1) , rootd(1) More information can be found at the ROOT website: http://root.cern.ch <http://root.cern.ch> ORIGINAL AUTHORS
The ROOT team (see web page above): Rene Brun and Fons Rademakers COPYRIGHT
This library is free software; you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as pub- lished by the Free Software Foundation; either version 2.1 of the License, or (at your option) any later version. This library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MER- CHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details. You should have received a copy of the GNU Lesser General Public License along with this library; if not, write to the Free Software Foun- dation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA AUTHOR
This manual page was written by Christian Holm Christensen <cholm@nbi.dk>, for the Debian GNU/Linux system (but may be used by others). ROOT
Version 3 PROOFD(1)
All times are GMT -4. The time now is 06:41 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy