Set up FSS for two projects: database and appserver. The database project has 20 CPU shares. The appserver project has 10 CPU shares.
hostname# cat /etc/project
. . . user.database:2001:database backend:admin::project.cpu-shares=(privileged, 20,deny) user.appserver:2002:Application Server frontend:admin::project.cpu-shares= (privileged,10,deny) . . .
The line break in the lines that precede “20,deny” and “(privileged,” is not valid in an /etc/project file. The line breaks are shown here only to allow the example to display on a printed or displayed page. Each entry in the /etc/project file must be on a single line.
If the FSS is enabled but each user and application is not assigned to a unique project, then the users and applications will all run in the same project. By running in the same project, all compete for the same share, in a timeshare fashion. This occurs because shares are assigned to projects, not to users or processes. To take advantage of the FSS scheduling capabilities, assign each user and application to a unique project.