Skip Navigation and go to content
University of North Texas Computing Center Computing Center Logo
Computing Center Home
Help Desk
Training
About Us
Publications
Our Mission

 



Sol Policies


Below is a listing of the policies on this system. For a listing of the general policies on this campus, see University-wide Computing Policies & Procedures.


Table of Contents


1) Resource Utilization

1.1) Processor Utilization

A Computationally Intensive Job is one that requires more than 60 minutes of processor time. Such jobs typically consume more than 50% of processor utilization. Users are allowed only one Computationally Intensive Job at a time. Additional jobs of this nature will be termintated.

All Computationally Intensive Jobs must be run with a "nice" value of at least 10. All supported shells have been configured to use /usr/bin/nice. So, to correctly nice an interactive job, simply do the following:

% nice job        (for tcsh or csh)
$ nice job        (for bash or sh)

Non-interactive Computationally Intensive Jobs that are to be run in the background can be started using the following commands:

% nice job &         (for tcsh or csh)
$ nohup nice job &   (for bash or sh)

The bash and sh shells require nohup if the job is to proceed after logging out. Unless explicitly redirected, all output, including errors, for the command started with nohup will go into the file "nohup.out". To explicitly redirect the output under bash and sh, do the following:

$ nohup nice job > out 2> err &

Using this command, all standard output will go into the file out while all errors will go into the file err.

Redirection under the tcsh and csh shells is similar, but standard output and standard error cannot be redirected to different locations quiet so easily. To run a background job with redirection under these shells, do the following:

        
% ( nice job > out ) >& err &

If you have any questions about a particular shell syntax, call 565-2324 or send E-Mail to helpdesk@unt.edu.

1.2) Memory Utilization

A Memory Intensive Job is one that has a combined data and stack size greater than 128 MBytes or uses 20% or more of real memory. Using the command /usr/ucb/ps -vx, the combined data and stack size for each process is shown under the "SIZE" column while the memory usage is shown under the "%MEM" column.

There is a limit of one Memory Intensive Job at a time per user. Jobs that exceed this limit may be terminated.

1.3) Exceptions

Exceptions to the above policies must be obtained at least 24 hours in advance and are only available through the Computing Center office during regular office hours.


2) Privacy Considerations

Commands like ps, top, w, and who are unrestricted.


3) Use of Servers

3.1) Definition of Server

A server is any process that has the potential of providing any resources to users other than yourself. This includes users on the same system or users on other hosts on the Internet.

3.2) Restriction on Servers

User-run servers of any kind are not allowed on this system. Sol is meant to provide computing resources to campus researchers. It is not meant to provide a server for resources to the general Internet community.


4) Account Sharing

Letting someone else use your account is against University policy. The policy prohibits all users from sharing accounts, logging into an account to allow someone else to use it, and sharing passwords.

If you suspect that someone may have broken into your account, please let us know, and change your password as soon as possible.


5) Account Expiration

Faculty/Staff/Student account eligibility expires immediately upon termination of employment or enrollment.


6) Use of .rhosts file

The use of the "+" entry in an .rhosts file is prohibited on this system. Use of .rhost files is discouraged.

The Account Sharing policy also applies to the use of .rhosts files.

For more information on the use of .rhosts files, see the on-line manual: man rhosts.


7) Using /tmp

Please do not save any files to /tmp. Use /scratch for downloading files. /tmp just isn't large enough, and if it gets full, basically everyone on the system has to wait until the space is cleared up.

From /tmp/URGENT.README.FIRST:

     DO NOT manually place any files in this 
     directory (/tmp).  This space is
     reserved solely for utilities that must 
     create temporary files.  It is not
     intended nor is large enough to be used 
     as personal scratch space.  If you
     need some temporary scratch space, please 
     use /scratch, that's what it's 
     there for.  Any files placed on /tmp will 
     be deleted without notice.

8) Using /scratch

The /scratch partition has been provided for temporary disk space. It can be used to upload/download files to and from the net, your account, or your machine at home. However, this is only for temporary use. It is not meant to be used as an archive. Files on this partition that are older than 3 days may be deleted at any time to recover space. Backups are not made of any of the files on this partition. Anything lost or deleted from this partition cannot be restored. .


9) Appropriate Use

Accounts granted on UNT machines can only be used for academic purposes. In particular, UNT accounts, including those on Sol, cannot be used for conducting official commerce. Sol services are provided to faculty and students for the benefit of their research activities while at UNT. These resources cannot be used to subsidize commercial businesses.


10) Quota Allocation

Because disk storage resources are limited, a quota system is in place for user storage on Sol. Researchers are granted 20 Megabytes of quota in the /home partition of Sol for the storage of programs and data. A one-time quota increase to 40 Megabytes is available upon request, if the need arises. Requests for quota allocations beyond 40 Megabytes can be directed to Dr. Philip Baczewski, Director of Academic Computing and User Services, along with an estimate of the amount of allocation needed and the estimated duration of the need. Allocations will be made on a space-available basis in the order that they are received.



Return to ACS-Supported UNIX Systems
Return to ACS

This document last updated by: Philip Baczewski


Computing Center Home | Help Desk | Training
About Us | Publications | Our Mission

Site was last updated or revised : 07/05/00

UNT home page | Search UNT | UNT news | UNT events

 

 

Computing Center Home