PsotLogin and PostSession scripts for Solaris

8 More Discussions You Might Find Interesting

1. 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...

2. 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...

3. 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...

4. 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

5. 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....

6. 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?

7. 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...

8. 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

LEARN ABOUT POSIX

s390_runtime_instr

S390_RUNTIME_INSTR(2)						System Calls Manual					     S390_RUNTIME_INSTR(2)

NAME

       s390_runtime_instr - enable/disable s390 CPU run-time instrumentation

SYNOPSIS

       #include <asm/runtime_instr.h>

       int s390_runtime_instr(int command, int signum);

DESCRIPTION

       The s390_runtime_instr() system call starts or stops CPU run-time instrumentation for the calling thread.

       The   command  argument	controls  whether  run-time  instrumentation  is  started  (S390_RUNTIME_INSTR_START,  1)  or  stopped	(S390_RUN-
       TIME_INSTR_STOP, 2) for the calling thread.

       The signum argument specifies the number of a real-time signal.	The real-time signal is sent to the thread if the run-time instrumentation
       buffer is full or if the run-time-instrumentation-halted interrupt occurred.

RETURN VALUE

       On  success,  s390_runtime_instr() returns 0 and enables the thread for run-time instrumentation by assigning the thread a default run-time
       instrumentation control block.  The caller can then read and modify the control block and start the run-time instrumentation.  On error, -1
       is returned and errno is set to one of the error codes listed below.

ERRORS

       EINVAL The value specified in command is not a valid command or the value specified in signum is not a real-time signal number.

       ENOMEM Allocating memory for the run-time instrumentation control block failed.

       EOPNOTSUPP
	      The run-time instrumentation facility is not available.

VERSIONS

       This system call is available since Linux 3.7.

CONFORMING TO

       This  Linux-specific  system call is available only on the s390 architecture.  The run-time instrumentation facility is available beginning
       with System z EC12.

NOTES

       Glibc does not provide a wrapper for this system call, use syscall(2) to call it.

SEE ALSO

       syscall(2), signal(7)

COLOPHON

       This page is part of release 4.15 of the Linux man-pages project.  A description of the project, information about reporting bugs, and  the
       latest version of this page, can be found at https://www.kernel.org/doc/man-pages/.

Linux Programmer's Manual					    2017-09-15						     S390_RUNTIME_INSTR(2)

Solaris