From owner-pagg@oss.sgi.com Tue Feb 20 05:36:24 2001 Received: by oss.sgi.com id ; Tue, 20 Feb 2001 05:36:15 -0800 Received: from mail.uni-kl.de ([131.246.137.52]:58343 "EHLO mail.uni-kl.de") by oss.sgi.com with ESMTP id ; Tue, 20 Feb 2001 05:35:58 -0800 Received: from schummi.rhrk.uni-kl.de (IDENT:root@schummi.rhrk.uni-kl.de [131.246.91.211]) by mail.uni-kl.de (8.11.0/8.11.0) with ESMTP id f1KDZtB07068 for ; Tue, 20 Feb 2001 14:35:55 +0100 (MET) Received: (from schummer@localhost) by schummi.rhrk.uni-kl.de (8.11.0/8.11.0) id f1KDZt201125 for pagg@oss.sgi.com; Tue, 20 Feb 2001 14:35:55 +0100 Message-ID: X-Mailer: XFMail 1.4.4 on Linux X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Tue, 20 Feb 2001 14:35:55 +0100 (CET) X-Face: i5 To: pagg@oss.sgi.com Subject: No accounting records Sender: owner-pagg@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;pagg-outgoing Hello! I have installed CSA on my linux system (Redhat 7.0). But no accounting records are collected as the output of "csacom -W" shows: ACCOUNTING RECORDS FROM: Tue Feb 20 11:35:03 2001 COMMAND START END REAL CPU MEAN CORE MEAN VIRT NAME USER TIME TIME (SECS) (SECS) SIZE (KB) SIZE (KB) *** No Process records selected Output of "csacom -W": Day 0: Tue Feb 20 11:35:03 2001 - first record. Day 0: Tue Feb 20 14:29:26 2001 - last record. "csaswitch -c status:" # Accounting status for Tue Feb 20 14:34:07 2001 # Name State Value csa On nqs Off wkmg Off tape Off mem On io On memt Off time Off "lsmod": Module Size Used by vmnet 16800 1 vmmon 17700 0 (unused) csa_acct 13116 0 job 15560 0 [csa_acct] 3c59x 22812 1 (autoclean) esssolo1 24108 1 soundcore 3652 4 [esssolo1] What is wrong? Any suggestions? Mit freundlichen Gruessen / Best Regards Hans J. Schummer *********************************************************************** * Universitaet Kaiserslautern * Telefon 0631/205-2436 * * - R H R K - * Telefax 0631/205-3056 * * Abteilung Hochleistungsrechnen * Telex 4-5627 unikl d * * Postfach 3049 * e-mail schummer@rhrk.uni-kl.de * * D-67653 Kaiserslautern * * Germany * * WWW: http://hlrwm.rhrk.uni-kl.de/home/mitarbeiter/schummer.html * *********************************************************************** From owner-pagg@oss.sgi.com Tue Feb 20 07:41:45 2001 Received: by oss.sgi.com id ; Tue, 20 Feb 2001 07:41:36 -0800 Received: from deliverator.sgi.com ([204.94.214.10]:25882 "EHLO deliverator.sgi.com") by oss.sgi.com with ESMTP id ; Tue, 20 Feb 2001 07:41:14 -0800 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id HAA03266 for ; Tue, 20 Feb 2001 07:40:05 -0800 (PST) mail_from (watters@sgi.com) Received: from tulip-e185.americas.sgi.com (tulip.americas.sgi.com [128.162.185.208]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA852486; Tue, 20 Feb 2001 09:39:52 -0600 (CST) Received: from sgi.com (watters@paradox.americas.sgi.com [128.162.195.127]) by tulip-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id JAA88797; Tue, 20 Feb 2001 09:39:52 -0600 (CST) Message-ID: <3A928FC6.4264369B@sgi.com> Date: Tue, 20 Feb 2001 09:39:50 -0600 From: Sam Watters Organization: SGI X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.16-4SGI_29 i586) X-Accept-Language: en MIME-Version: 1.0 To: schummer@rhrk.uni-kl.de CC: pagg@oss.sgi.com, kohnke@sgi.com Subject: Re: No accounting records References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-pagg@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;pagg-outgoing Hans, Did you add the entries to the appropriate PAM configuration files? On the distributions I am familiar with (Turbolinux and Redhat) those files are in the /etc/pam.d directory. You need to add the following line to each of those files that configure services for which you want new jobs to be created. For example, here is what my /etc/pam.d/login files looks like on one of my systems: [watters@paradox watters]$ cat /etc/pam.d/login #%PAM-1.0 auth required /lib/security/pam_securetty.so auth required /lib/security/pam_pwdb.so shadow nullok auth required /lib/security/pam_nologin.so account required /lib/security/pam_pwdb.so password required /lib/security/pam_cracklib.so password required /lib/security/pam_pwdb.so nullok use_authtok session required /lib/security/pam_pwdb.so session optional /lib/security/pam_job.so session optional /lib/security/pam_console.so [watters@paradox watters]$ The /lib/security/pam_job.so entry is the one to be added to support job creation for the login process. This will cause login to create a new job whenever it is used as the service for entry onto the system. I suggest using the "optional" parameter until you feel comfortable with the behavior of job creation. Then you should change it to "required". I have added this entry to the following files on my system (in /etc/pam.d directory): [watters@paradox pam.d]$ fgrep pam_job.so * ftp:session optional /lib/security/pam_job.so gdm:session optional /lib/security/pam_job.so kde:session optional /lib/security/pam_job.so login:session optional /lib/security/pam_job.so mcserv:session optional /lib/security/pam_job.so passwd:session optional /lib/security/pam_job.so rlogin:session optional /lib/security/pam_job.so rsh:session optional /lib/security/pam_job.so su:session optional /lib/security/pam_job.so xdm:session optional /lib/security/pam_job.so -- Sam Watters Resource Mgmt Team SGI watters@sgi.com