Perl scripts need to be executable in order to run them on the server. You can do this using the ftp software you use to upload your files. Upload the files in the usual way, then perform the following on the uploaded file: In WS_FTP: right click on the file and choose "FTP commands", then "SITE". Type in: In CuteFTP: right click on the file and choose "Change File Attributes". In the manual section type 755 and press OK.

Yes, just bundle your glade files as resources (using the -resource: option in the compiler) and change your constructor call or use the Glade.XML.FromAssembly () method to create your Glade.XML ui.

It is not necessary, or possible to change files/folder permissions. We have all of our web servers set up in the same way for files/folder permissions. All necessary permissions are available to customers for use on their web site, no changes are necessary to get applications to work. The technical explanation of how we set up permissions is this. For each website we host we create a user account specifically for that website.

You will need to request that the proper permissions be set on your web site by contacting the Tivilon Support Team. Once we change the permissions on your web site, you do not have to set permissions or chmod any files or directories. There is no additional charge for Tivilon to activate CGI scripting on your web site.

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.

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!

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.

Your FTP client program will have built into it the ability to CHMOD. This is UNIX speak for making a file executable. Locate the CHMOD capability of your FTP program and then select the file you need to make executable, then click the CHMOD button (or however your FTP client program accomplishes this) and set the file to be executable using the numbers 755 or click the "x" box in first of the three columns of numbers that may be listed.

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.

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.

Not yet, we are working on making a secure framework for permissions to allow individual connections to external IM networks, file transfers and web conferences.

mentioned above, the Internet Guest User Account must have Read and Execute on the component DLL. For any component that is reading a file, IUSR_machine_name must have read permission for that file. If the component is creating a file or writing to a database, IUSR_machine_name must have write permission for the appropriate directory. If files are being deleted it will need Full Control.

There is a section of the Installation Guide devoted to this topic, but basically you must ask your server's tech support people to do it for you. There is no way I know of to remotely set permissions under Windows. Send them a short email describing the settings you need and where the directories are.

If you want to give user foo, permissions baa recursively, the way to do it is: find . -type d -exec fs sa {} foo baa \;

SA-FileUp executes in the same security context as IIS, which is typically as user IUSR_<machinename>. This is set using the Internet Service Manager. SA-FileUp can only write to files with this permission. Since SA-FileUp is writing to disk, it is suggested that you set permissions appropriately to disable write access by IUSR_<machinename> to inappropriate areas such as the Windows root directory. Also, SA-FileUp has a .