08-13-2010
Sorry my fault, even if I set to run it at specific time, it also didn't run, but I can run it manually. Not sure why.
10 More Discussions You Might Find Interesting
1. Programming
here's the problem, i have two processes that i need to run and both process should be run at a total of 1 minute each. how do i do that? and one more here's what the processes do: the 1st process show the '+" sign infinitely while the 2nd process displays the "-" infinitely. how could i count the... (1 Reply)
Discussion started by: kelogs1347
1 Replies
2. Solaris
Hi ,
I have a shell script to perform some actions on sun solaris box . This script normally requires to be run as a different user. so, whenever i have to run this script, i need to sudo in as that user , enter the password and execute it. Now,I have to setup a cronjob to execute the script... (11 Replies)
Discussion started by: csg_user
11 Replies
3. UNIX for Dummies Questions & Answers
Hi all
Recently i had finished a perl script. When i run manually, the script work fine.
But when i wanted to put the script in cron, it didn't get the same output as it run manually. I felt that it only execute the script until certain line then it stop as i see most of the related files didn't... (6 Replies)
Discussion started by: AirWalker83
6 Replies
4. Shell Programming and Scripting
Hi
Im very new at working with unix and this problem I simply can not understand. I know there are a lot of threads about problems with shell scripts behaving differently when run from a terminal and from a cronjob. I have tried everything(almost) but I still havent cracked this problem.
Im... (15 Replies)
Discussion started by: Nightowl
15 Replies
5. Shell Programming and Scripting
I am using Solaris 9. I wish to run my script every 1 minute inteval. Though i can run it using below entry in crontab.
* * * * /export/home/username/script/file_exist_&_run.sh
in short above script will check whether a specific file exist in a directory. If it found it will inovke another... (10 Replies)
Discussion started by: thepurple
10 Replies
6. UNIX for Dummies Questions & Answers
Hi can any one help me out.
while running crontab , m getting error bad minute time..
how to resolve this error.
i created 1 txt file a.cron
mirrordir -vm \home\t \homet1
& i saved it.
then i created a crontab file ..with
crontab -e
& i added a line in it.
* 1 * * * \root\a.cron
& i save... (2 Replies)
Discussion started by: unxdost114
2 Replies
7. Shell Programming and Scripting
Hi All,
How to schedule a shell script(script name- byweeklyreport.sh) it should run by weekly in corn job or is there any script have to write to check week and then run the above script.
example-1st run March 06 2013
2nd run March 20 2013
3rd run April 3 2013... (13 Replies)
Discussion started by: krupasindhu18
13 Replies
8. UNIX for Dummies Questions & Answers
Hello,
I have two crontabs, one for the root and one for another user. There is a script in my configurations that has to send a email. The script works and sends the emails when I run it by hand with either the root or the user, and when I program it in the root's crontab.
But! It does not... (3 Replies)
Discussion started by: Tralaraloro
3 Replies
9. Shell Programming and Scripting
when it runs and look at my acron.log file it generates an error as below
/tmp/prog.sh: line 4: (12 Replies)
Discussion started by: azherkn3
12 Replies
10. UNIX for Advanced & Expert Users
Hi,
I am trying to bring down the application gracefully before bringing down AIX OS/LPAR using RC directories.
Issue: Application script is not working properly during/before AIX OS/LPAR shutdown. looks like "rc.d" directories doesn't recognize Kill script.
But Startup script (using... (0 Replies)
Discussion started by: System Admin 77
0 Replies
LEARN ABOUT OSF1
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)