Home ยป Computer Support

Computer Account Policies

These policies apply to all users with accounts on the CGRB file server. More stringent and specific policies apply to users of the computational infrastructure.

  1. File System Usage

    1. Do not run programs or scripts on the CGRB file server. This is because:
      • it is a file server and is not tuned for CPU-intensive tasks
      • executables that go awry could potentially affect other users' work
    2. Store only work documents and data on the server. More specifically:
      • Do not backup your personal computer files to the server (for example: profile information, executables, music, video)

  2. Security

    1. Acceptable Use Policy

      Oregon State University has an acceptable use policy (AUP) that we follow. We recommend that you read and understand the implications of this document on your computing resources.

    2. Password

      1. Good/Bad password

        A good password contains at least seven characters with at least one capital letter and one number. A good way to create a password is to think of a phrase and convert the first letter in each word of the phrase to a letter. For example, "The Seattle Seahawks win when #37 runs!" would make a password of "TSSww37!" (without the quotes). It's an opportunity to use your creativity!

      2. Multiple passwords

        It's a good idea to maintain separate passwords for web accounts and for computer accounts. This will limit the exposure of your computer accounts in the less-secure computing environment that comprises the web.

      3. Physically secure

        We strongly recommend that you do not write down or otherwise store your non-web login credentials that tend to number only 2 or 3. A password on a sticky-note hanging from your computer display is very bad style. If you must write down your non-web account information, be sure to secure them in a locked drawer or well-hidden location. Web-based logins proliferate and it is expected that you keep a record of these accounts (but not on a networked computer).

      4. Usage

        Do not use tools or scripts to automate logins. This exposes your login credentials as clear-text before an encrypted session has initiated. If you require this type of capability for a project then contact CGRB Support.

  3. Accounts

    For information on acquiring a CGRB account see accounts.

    1. Core Labs Ordering Site

      We monitor activity on accounts used for ordering Core Labs services. If we notice that an account has been inactive for at least one year, we will contact that user to determine if the user is still working at that lab. If not, the account will be deactivated to protect the interests of that user's lab.

    2. FS_MAIL Guest Accounts

      We provide file space in the IncomingData directory so that users can temporarily store files generated from scanners, the confocal microscope, etc. These files are backed-up nightly and will reside on disk for a minimum of 3 months. After 3 months, these files may be marked for deletion if we need to free up some space.

  4. Web Applications

    1. We only support production-quality software on both servers and clients. This means that we will not run beta software on a production server. Likewise, we will not support clients such as beta versions of web browsers.
    2. It may also be the case that an old version of a supported browser will not work with a particular web-based application. It would be best for you to try another browser to verify whether the problem is related to a browser version before contacting us so you can give us this information.

  5. Email

    1. We do not allow users to blind copy (BCC) moderated email lists. There are several reasons for this policy. Significantly, members of a group want to see what list was addressed for context and to filter incoming mail whereas mail to "undiscosed-recipients" looks like spam.
    2. We do not have an upper bound defined for a user's Inbox. However, if we find that a user's inbox is confounding the mail server we may need to move it (deactivate it) to restore mail.

  6. Server Backup

    1. Incremental backups are run nightly on a disk media on CGRB servers. Differential backups are run weekly. Full backups are bimonthly. User account data on the CGRB file server (cgrb.oregonstate.edu) is also written to tape every six months and stored into perpetuity.
    2. To request a file restore, send a note to support@cgrb.oregonstate.edu indicating the machine name, files, and, if relevant, the date of the files that you need to be restored.