🚀 go-pugleaf

Against my better wishes I have to implement a `project' based accounting
system on top of the standard AT&T Unix process accounting.  Projects are
represented by arbitary eight character text strings (which could be mapped
to small integers in the implementation) and each process that executes has
to be associated with one such string.  Projects can have one or more users
and each user can be a member of one or more projects (but only one project
at a time.) Users have to be able to change projects at any point with a
command and all subsequent processes executed in the same login session
have to be associated with the new project. 

I don't really want to modify the Unix kernel unless it is absolutely
necessary.

So far the best idea anyone has suggested is using the Unix groups as
projects but I dislike using groups for two disjoint purposes (the project
structure would impose restrictions on how users could share files is one
obvious problem.) 

Has anyone had to do something similar and is willing to share their
experiences?
-- 
Geoff. Lane.                                  Janet: zzassgl@uk.ac.mcc.uts
UTS Sys Admin, Manchester Computing Centre, Oxford Rd, Manchester, M13 9PL