If you want to use the language editing features you will need to set write permissions for all of the files in the ./languages folder If you want to upload media files using the upload media section of the admin menu then you need to set write permissions for your ./media and ./media/thumbs directory If you want to edit your gedcom file online, the gedcom file must have write permissions set for the PHP user. The method to set write permissions varies depending on your server configuration.

To change the permissions of files/directoies, issue the command "chmod" at the UNIX command prompt followed by the three digit number and filename. Here is a list of what numbers are assigned when setting permissions and the UNIX command.

On a unix server, every directory and file possess certain rights or permissions as to who can access the directory or file and what kind of access is allowed. This property give you a level of security regarding unauthorized use of your web site's resources. FTP into your website and travel to the directory containing the file for which you wish to set permissions. Highlight the file, and click the right mouse button.

Because web server operating systems place a heavy emphasis on who is allowed to Read, Write, and Execute files and scripts on your server. This is for security purposes. In Easy Availability there are a couple of files that need to be marked as 'Writeable' in order for the program to work.

Note: All of these commands should be executed at the telnet (dollar sign) prompt that you see right when you log in to osprey. Type "man chmod" for more information on setting permissions. In order for the World Wide Web program (called the HTTPD) to access your files, you have to make sure that it has permission to do so. With most accounts, you will probably not have to change anything.

These permissions are the afs Access Control Lists, or ACLs. You can set (and list) these with the "fs" command. To list the ACL for a particular directory, use the command: where "directory" is the directory we're changing, remembering that you can always use a period to indicate the current directory, "user" is the uniqname of the person we are permitting (or depermitting) the directory to, "rlidwka" is any combination of that list of letters, which are explained below.

Most FTP software will allow you to change the permissions of files and directories on unix web servers. For example, if you are using CuteFTP you can right click on the desired file or directory in the remote window and select 'Change File Attributes'. From here you will be able to set "read, write and execute" permissions for the "owner, group, and public". You are considered to be the owner, and everybody else is considered to be public, including your ISP's web server and perl.

The operator performing the backup requires the "back up files and directories" user right. This can be given directly using user manager, or the preferred way is to make the user a member of either the Administrators group or the backup operators group.

Unix systems are designed for multiple users, and include provision for protecting your work from unauthorised access by other users of the system. The file permissions determine who is permitted to do what with your programs, data, and directories. The command that sets file permissions is chmod. Web servers typically run as user "nobody".

CGIs must be set with executable file permissions, or requests for the script from the web server will result in an Internal Server error. Scripts that need to be executable should have their permission set with chmod 755. This sets the file's permissions so that the file's owner may read, write, and execute the file; and anyone else can only read and execute it.

Is there a command in TNOS to stop certain mail areas being broadcast with the MAILFOR beacon? I have some message areas I do not want broadcasting over the air!

You set forum permissions from the administration control panel -> Forums -> Permissions. This system has two modes of operation; Simple and Advanced. Simple uses a set of pre-defined authorisation levels, these set each type of authorisation setting to a specific level. Advanced settings allow you to specify individual levels for each operation in each forum. Experiment!

You have the opportunity to set the permission in the uploading page and also later on in the editing page. (If you don't know where those pages are located, read the questions above) Note if you make your submission private, no one will be able to search for your entries.

File permissions are the system's way of telling you what you can and cannot do with a file or folder. They are governed by Access Control Lists (click for definition). There are two ways of setting file permissions. You can do it the graphical way or the command-line way. To do it graphically, you must have Simple File Sharing disabled from the View tab of Folder Options (Professional only) or be in Safe Mode (either). Right-click on the object of your choice and click Properties.

Typically, when Log::Log4perl::Appender::File creates a new file, its permissions are set to rw-r--r--. Why? Because your environment's umask most likely defaults to 0022, that's the standard setting. What's a umask, you're asking? It's a template that's applied to the permissions of all newly created files.

Yes. Most FTP programs will allow this. Alternatelty, you use the file manager from the control panel to navigate to the file whose permissions you want to change and you can set read and write permissions as you please. 755 is typical for scripts you want to execute. Click all boxes in the first column, and the first and last boxes in the other two columns to achieve this.

Your scripts should be set to file permission 750 as this will provide the best security. Any data files that are accessed by your own scripts should have their permissions set to 600 so that only you (and your scripts) can read and write the file. Nobody else on the system (and their scripts) will be able to access your file. This is very important if your files contain sensitive information, like credit card numbers. BigBiz offers PHP scripting as an alternative to CGI scripting.

Try to have as few users access the repository as possible. For example, run apache or 'svnserve -d' as a specific user, and make the repository wholly owned by that user. Don't allow any other users to access the repository via file:/// urls, and be sure to run 'svnlook' and 'svnadmin' only as the user which owns the repository. If your clients are accessing via file:/// or svn+ssh://, then there's no way to avoid access by multiple users.

It depends on your FTP client. The easiest way for you is to login to your control panel, find 'File Manager' and change permissions with this 'File Manager' (if you have such option).

These are set from Admin -> Users (Groups) -> Permissions. The system may appear strange but it's very powerful. When you look up a user or group it will give you basic information (at the top of the page) followed by the available forum listing and current settings for this user. You can assign moderator status to users and groups and if you have PRIVATE forums (or forums with any of their individual operations set to PRIVATE) you can also assign access.

Answer: CGIs must be set with executable file permissions, or requests for the script from the web server will result in an Internal Server error. Scripts that need to be executable should have their permission set with chmod 755. This sets the file's permissions so that the file's owner may read, write, and execute the file; and anyone else can only read and execute it.

To maximize security, you should adopt a strict "need to know" policy for both the document root (where HTML documents are stored) and the server root (where log and configuration files are kept). It's most important to get permissions right in the server root because it is here that CGI scripts and the sensitive contents of the log and configuration files are kept. You need to protect the server from the prying eyes of both local and remote users.

The script requires that all files being used by it are set to 755. Anything higher will work, but isn't safe. If it's lower you will most likely run into problems with the script.

The spool directory needs to have ownership and permissions set correctly. Normally, this directory has owner root and group mail, and has permissions set drwxrwxr-x or drwxrwxrwt. (The second form sets the sticky bit to prevent non-owners from deleting or renaming files.) The first form of the second command sets permissions so that only user root or group mail can create or write files.

Frontpage allows users to determine what kind of access outsiders have in their web. To set to permissions, right click the specific folder in the "All Folders" window (left side of the screen) and then click on properties. The properties box will have three check boxes on the bottom. They each perform the following functions: Allow scripts to be run- This permits scripts written in ASP and PerlScript to be run. Otherwise your ASP pages will be non-functional.

Windows servers do not require any file permissions, but your web server must allow CGI programs to execute, and your script must be able to read and write to the folders you define for authentication, customer data, photos, and working data. UNIX servers do require file permissions, but requirements can vary from server to server. Normally all the scripts should be set to 755 with the exception of config.pl and common.pl, which can be set to 644.