User Classes Each OpenBSD user has a login
User Classes Each OpenBSD user has a login class that defines limits on that user’s access to system resources, how their environment behaves, and how users in that class authenticate. When you change the characteristics of a class, those limits affect all users in the class. All login classes are defined in /etc/login.conf. You can change a user’s class by running “chpass username” as root. Just put the class name in the “class” space provided, as shown in “Editing Users.” The Default Login Class Whenever you create an account with adduser(8), that user is automatically assigned to the “default” class. The simplest way to manage login classes is to have the default class be the most commonly used class on your system. If your computer is an email server with a handful of administrators and several hundred mail users, set up the default class appropriately for the common case the mail users. You can manually change the administrator’s classes to a more appropriate one more easily than you can edit all those hundreds of users. Class Definitions Each class definition consists of a series of variable assignments. When a user logs in, login(1) uses these variables to establish the user’s resource limits and environment setup. Each entry in the class definition begins and ends with a colon, although technically, each entry is all one line. The backslash character is a continuation marker, indicating that the computer should ignore the line break. Humans don’t like 500 character lines of text, after all! The standard /etc/login.conf starts with the “default” class. This gives the average user fairly broad access to the system. If you’re running a modern system with gigabytes of RAM, you might find them too restrictive. If your OpenBSD box is a Pentium 166, however, these settings will basically give every user unlimited access to all system resources. If users consuming resources is a serious concern, you might well want to edit these settings. Here’s a sample of the beginning of a login class. default: :path=/usr/bin /bin /usr/sbin /sbin /usr/X11R6/bin /usr/local/bin: :umask=022: :datasize-max=256M: … There are many more variables in a login class, but this should be enough to give you the idea. You can completely change a user’s experience by assigning him to the class that configures his login environment as you desire. Some login.conf variables don’t have a value; they change account behavior just by their presence. For example, the “requirehome” variable just needs to be in the class definition to have effect. :requirehome: Legal Values for /etc/login.conf Variables You can give any of the following values to a login.conf variable assignment. . Afull path to a text file. . A comma-separated list of values. . A number. . A space-separated list of path names. If a ~ is the first character in a path name, the ~ is replaced by that particular user’s home directory. . A full path to a program. . A size, either in bytes (default), kilobytes (k), or megabytes (m). . A time, in seconds (default), minutes (m), hours (h), days (d), weeks (w), or years (y). Page 139
Note: If you are looking for cheap and quality provider to host and run your java application check Astra java hosting services