Sponsored Content
Operating Systems Solaris PsotLogin and PostSession scripts for Solaris Post 302550622 by jimx on Friday 26th of August 2011 11:04:57 AM
Old 08-26-2011
Thanks for the help guys.

To achenle, in short, the accounting is a small part of this project. Also, the Solaris built in accounting system does not fit our needs.

To psshah,
1) The instrument controller computers do not shut down. Users only need to login to use the instrument and then logoff when they are done. Sometimes we have to shut down the computers but that is rare.

2) GUI

3) There are over 20 instruments in our facility. There is a program (written in vb.net) running on a windows computer in our main office which is monitoring the login/off activities of all the instruments (basically monitoring the log.txt made by the login/off script of that instrument). Whenever the program detects a user finishes the experiment and logoff the instrument, a few things will be done instantly. Two examples, 1) the usage information will be collected instantly. By adding other information (user name, research group, account #, time, cost, etc), a new entry will be added to a billing database which will be processed monthly. 2) The user's newly save data will be located and uploaded to a cloud storage (for data backup, or user can process data in his/her lab).

In fact this system has been running for a while, except the two Solaris instruments which I still don't know how to get login/off information instantly from our main office.

Thanks again for any advice.
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

kill scripts under Solaris

I should know this, but do K scripts in the /etc/rc?.d directories get run in numerically ascending or descending order? By default there are none in rc3.d. Is it OK to put 2 in there, and will they be run first (which is my goal). Thanks, Chuck (1 Reply)
Discussion started by: 98_1LE
1 Replies

2. UNIX for Advanced & Expert Users

scripts no longer running (solaris 8)

hello: I am a somewhat experienced unix user, but brand new to this forum. I am encountering a strange new problem. I have a shell script called foo.ksh it has been running for years (literally) on my Sun (Solaris 8) machine. Recently we put a version of samba on this machine to... (3 Replies)
Discussion started by: smcadoo
3 Replies

3. Solaris

Solaris login scripts

I've got Solaris 9. I've read that I can do a login script for each individual user with the .postlogin file, but is there not a way to set up something like that from a group-membership level? If there is, how can one trace down what group membership login scripts are being run? (0 Replies)
Discussion started by: citrowske
0 Replies

4. Shell Programming and Scripting

2 shell scripts in Sun Solaris

Hi, Can somebody pls help me? I need to write 2 shell scripts in Sun Solaris operating system which would do this: 1. go to the specified directory - I am using alias for it at the moment 2. start the particular sql script with the output log as same as the script but with timestamp e. g.... (4 Replies)
Discussion started by: balco
4 Replies

5. Solaris

Scripts in solaris server

hi, i want to know whether we can use both perl and unix shell in a single script in Solaris server (4 Replies)
Discussion started by: chn10db001
4 Replies

6. Solaris

Solaris 10 startup scripts

Hi all, I have a server in maintenance mode and need to boot it up. Its due to a broken service "RepX". I need to stop the service from trying to start at boot up but i can't find where it is booting up from... it is not in any of the rcX.d directories and the two locations i have found it... (6 Replies)
Discussion started by: Tommyk
6 Replies

7. Solaris

Moving directory structure and scripts from HP to Solaris

Hi, I am presently working in a migration project from HP Unix to Sun Solaris. I need to place all the directory structures, shell scripts and users into Sun Solaris. By doing this task manually there is a possibility for discrepencies. So any tools are there to do these kind of... (4 Replies)
Discussion started by: nag_sathi
4 Replies

8. Solaris

When were all scripts on the Solaris server last executed?

Hi All, I am new to this forum and I am hoping someone will be able to help me:) I have inherited a very old Solaris server that has a number of scripts around 500 in total. I need to migrate the scripts to Linux but I would like to know which ones are currently being executed rather... (10 Replies)
Discussion started by: josamy
10 Replies
acct(1M)																  acct(1M)

NAME
acct: acctdisk, acctdusg, accton, acctwtmp, closewtmp, utmp2wtmp - overview of accounting and miscellaneous accounting commands SYNOPSIS
file] file] [file] reason DESCRIPTION
Accounting software is structured as a set of tools (consisting of both C programs and shell procedures) that can be used to build account- ing systems. The shell procedures, described in acctsh(1M), are built on top of the C programs. Connect time accounting is handled by various programs that write records into the The programs described in acctcon(1M) convert this file into session and charging records which are then summarized by (see acctmerg(1M)). Process accounting is performed by the HP-UX system kernel. Upon termination of a process, one record per process is written to a file (normally The programs in acctprc(1M) summarize this data for charging purposes; is used to summarize command usage (see acctcms(1M)). Current process data can be examined using (see acctcom(1M)). Process accounting and connect time accounting (or any accounting records in the format described in acct(4)) can be merged and summarized into total accounting records by (see the format in acct(4)). is used to format any or all accounting records (see acctsh(1M)). reads lines that contain user ID, login name, and number of disk blocks, and converts them to total accounting records that can be merged with other accounting records. reads its standard input (usually from and computes disk resource consumption (including indirect blocks) by login. Only files found under login directories (as determined from the password file) are accounted for. All files under a login directory are assumed to belong to that user regardless of actual owner. If is given, records consisting of those file names for which charges no one are placed in file (a potential source for finding users trying to avoid disk charges). If is given, file is the name of the password file. This option is not needed if the password file is (See diskusg(1M) for more details.) turns process accounting off if the optional file argument is omitted. If file is given, it must be the name of an existing file, to which the kernel appends process accounting records (see acct(2) and acct(4)). writes a utmp record to its standard output if the option is not used. If the option is used, writes a record to The record contains the current time and a string of characters that describe the reason for writing the record. A record type of is assigned (see utmp(4) and utmps(4)). The string argument reason must be 11 or fewer characters, numbers, or spaces if option is not used. Otherwise, it must be 63 or fewer characters, numbers, or spaces. For example, the following are suggestions for use in reboot and shutdown procedures, respec- tively: writes a record, for each user currently logged in, to the file This program is invoked by runacct to close the existing file before creat- ing a new one. writes a record, for each user currently logged in, to the file This program is invoked by runacct to initialize the newly created file. FILES
Holds all accounting commands listed in section(1M) of this manual. Current process accounting file. Used for converting login name to user ID Login/logoff history file. New login/logoff history database. SEE ALSO
acctcms(1M), acctcom(1M), acctcon(1M), acctmerg(1M), acctprc(1M), acctsh(1M), diskusg(1M), fwtmp(1M), runacct(1M), acct(2), acct(4), utmp(4). utmps(4), wtmps(4). STANDARDS CONFORMANCE
acct(1M)
All times are GMT -4. The time now is 11:52 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy