UNIX Shell/Compiler Policy Acceptable Use Policy
Scheduled background processes (Cron and at jobs):
You may run 'cron/at' jobs no more often then twice an hour. You may only
run CPU or I/O intensive jobs in the early morning (between 1:00 a.m. and
8:00 a.m.). For performance reasons, run jobs at odd times (i.e. rather
then running at every half hour, run every 34 minutes or 29 minutes) --
this will avoid consuming the CPU/disks when other system processes may be
set to run.
Background processes (Bots, Servers, MUDs, etc...):
Each user is allowed to run one (1) background process while not
logged in. An IRC Bot is probably the most popular. We reserve the right
to kill off background processes during heavy load and memory usage
periods. Background processes must consume less then 10 seconds of cpu
time per hour (this sounds small, but not many things would ever use this
much cpu time during their entire run period), may not be disk intensive,
and must consume less then 890K (that is, kilobytes) of active (you don't
have to include what is swapped out) memory. An Eggdrop bot should be
able to run fine under these requirements.
Any user found running a server, bot, or other background process
(or foreground process, for that matter) for the purpose of interfering
with any user or system (inside or outside of FIX Net) will be frozen
indefinitely.
Users may NOT run MUDs or other servers at this time unless given
specific permission by FIX Net's Systems
Administrators.
The screen program
Those of you who use the screen program to setup multiple virtual
consoles need to be considerate of others and not detach sessions so you
can log out and pick them up where you left off later on. Screen eats
pseudo terminals and many users have a tendency to leave detached IRC
clients running, which take cpu and memory. Your help with this is
appreciated.
Temporary files and storage space:
Please use /usr/local/tmp (not /tmp) to hold temporary files.
/usr/local/tmp can store up to 100 megabytes and we encourage users to use
this rather then /tmp to avoid interfering with system processes that use
/tmp.
Users must delete temporary files after they are through with
them. Daily admin. scripts will clean out temporary files over a day old.
FIX Net does not charge for /usr/local/tmp usage, and any user found
abusing the privilege (i.e. trying to store files in /usr/local/tmp
permanently or repeatedly not cleaning out old temporary files after being
asked to) will be frozen indefinitely.
Ansi C Compiler (BSDI cc and GNU gcc) access:
Compiler access is currently restricted. If you have a reason
that you feel you need compiler access e-mail FIX Net's Systems
Administrators (netadmin@fix.net).
Users wanting access must show a proficiency in using the UNIX 'nice' command (we're not being funny here,
this is a real command).
