EWS Webperm

About
Webperm

      Webperm is a script to setup a homepage space on your personal EWS account. The webperm script allows you to easily change the file access settings on your EWS account web page. Command line parameters specify the exact action taken by webperm. webperm also has the ability to create a homepage for you!!

eesn6> webperm
Created "index.html" file in your "public_html" directory

      By default, webperm checks to see if you have a public_html directory in your home directory, sets public_html's permissions to be accessible to the web server, and attempts to create a ``template'' index.html file in your ~/public_html directory. If webperm sees an already existing index.html file it will prompt you for direction:

eesn6> webperm
File "public_html/index.html" already exists!
Do you wish to overwrite it? (yes/no): y
Created "index.html" file in your "public_html" directory

      All files have permission bits set to 0644 and all directories are by default set to 0711. See the man page on chmod(2) or the EWS Manual page for information on permission codes and manually setting these bits.

Type webperm -h at a prompt for a list of options.

Options

Most of these options are not meant to be used with each other.

-d -> disable

The -d option disables your EWS homepage.

Makes all webpages unreadable by removing execution permission from all directories within the public_html directory.

      This can be reversed by using webperm with its -t option enabled. This option is useful if you want to shut off your web pages while making major changes, or just plain don't want anyone to see your page(s). The webserver will report to browser:

Forbidden.
You don't have permission to access /~login/ on this server.

when someone tries to access your homepage.

-r -> (r)eadable directories

      The -r option makes the subdirectories in your public_html tree readable. This allows the webserver to generate a list of files in any directory in your webspace that does not have an index.html file in it. For example, say user janedoe had a data subdirectory in her public_html directory that she wanted to allow people to browse. Using the -r option with webperm, others could browse this directory through the webserver by going to the URL /~janedoe/data/ on her webserver.

-t -> no template

Suppresses creation of the index.html (t)emplate file, but otherwise sets permissions to be correct.

-W -> overWrite Without prompting

      Suppresses check for existing index.html file before creating the new one. Be careful with this one if you have an extensive index.html page that you would like to preserve.

-h -> help

This option prints out a summary of webperm's features.

Authors

Dave Crook         

Tim Lieder           


Back to the table of contents