csvisys@nike.ColoSpgs.NCR.COM (Susan Davis) (01/29/91)
I need help with UNIX accounting. We need to be able to do project level accounting on our Sun/Solbourne network. It is possible that a user could work on several projects during a given time frame. We do not want to force the users to use separate accounts for each project however it would be acceptable for the user the run a "change" script when they needed to change the project used during any login session. My understanding of the UNIX accounting software is that it can report CPU usage by process or username. My question is, does anyone know how I can associate the CPU of usera to the several projects he may have worked on during the accounting period? One idea I thought of was to have an entry in the passwd file for each user and each of his projects. So if usera worked on projectb and projectc each of these entries in the passwd file would point to the same home directory. I tried this with each account (usera, projectb and projectc) having the same UID and GID --- This resulted in the default user being whichever account was first in the passwd file regardless of which username I used to login. I also tried this with unique UIDs --- This caused access and protection problems. Is there anyway to have a "group" owned account with several users having access to the group files? I am not the most experienced UNIX user so any suggestions on my accounting problems would be most appreciated!! Thanks! -------------------------------------------------------------------------------- |Susan P. Davis, Design Services | >>>> Susan.Davis@ncr-mpd | |NCR Microelectronics | >>>> Susan.Davis@ColoSpgs.NCR.COM | |Colorado Springs, CO |>>>> (719) 596-5795 x435 VOICEplus 463-0435 |
clewis@ferret.ocunix.on.ca (Chris Lewis) (01/31/91)
In article <671@ncr-mpd.FtCollins.NCR.COM> csvisys%cad@MCC.COM (Susan Davis) writes: |I need help with UNIX accounting. We need to be able to do project level |accounting on our Sun/Solbourne network. It is possible that a user could |work on several projects during a given time frame. We do not want to |force the users to use separate accounts for each project however it would be |acceptable for the user the run a "change" script when they needed to change the |project used during any login session. Create a groupid for each project. Then, each user need only change group to the appropriate group (with newgroup) whilst working on the project. I believe that it's relatively easy to get standard System V to report per-group rather than per-user. -- Chris Lewis, Phone: (613) 832-0541, Internet: clewis@ferret.ocunix.on.ca UUCP: uunet!mitel!cunews!latour!ecicrl!clewis Moderator of the Ferret Mailing List (ferret-request@eci386) Psroff enquiries: psroff-request@eci386, current patchlevel is *7*.