11-09-2007
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I was wondering if itīs possible to cron job not to run on a certian day and time. Iīve got a job that runs everyday at 08:00
but would like it not to run on the 20:th between 08:00 and 10:00
Anyone know if this is possible, and if. How do i do it?
regards...
dOzY (3 Replies)
Discussion started by: dozy
3 Replies
2. UNIX for Dummies Questions & Answers
Where can someone find info on Cron Jobs? Very new to UNIX and the PC I inherited looks to have several of them. Looks like they are some kind of background program that runs automatically at specified times. Would like to delete some of them and know more about them. (6 Replies)
Discussion started by: dereckbc
6 Replies
3. UNIX for Advanced & Expert Users
I need to monitor my cron jobs with another unix machine since occasionally the cron will go down on the main server but there are no errors. Can anyone help with a script to write to use the cron on the back up machine to monitor the main server?
I am using SCO and the cron jobs have been... (3 Replies)
Discussion started by: rmarral
3 Replies
4. Solaris
I'm trying to run cron jobs to start any inhibited processes after a system reboot.
I can schedule th cron, but i'm confused as to how to incorporated the reboot, since reboot is scheduled at different times, once every month.
How can I write this to start every 15 min after after a reboot
... (2 Replies)
Discussion started by: Remi
2 Replies
5. Linux
I created a php script.
I'd like to have it run as a cron job every day at 10:30am. So i added
30 10 * * * /script.php to the cron file
Is it possible to run the script on the command line to test it out ? (1 Reply)
Discussion started by: dannyd
1 Replies
6. Solaris
how to Put a cron entry which should be same script triggered on every Saturday and 1st of every month at 01.00 GMT.
0 2 1 * 6 --( At 2.00 GMT every sat & on 1st of every month)
the above syntax is correct?
Thanks (1 Reply)
Discussion started by: kurva
1 Replies
7. UNIX for Dummies Questions & Answers
Hi,
We have a group of hosts using which the cron jobs are submitted...
Few days ago i had submitted a cron job in of these hosts, but unfortunately forgot the host name :(
Can anyone please help me out in finding this host name from which the cron s submitting the job, i dont want the... (2 Replies)
Discussion started by: bhavanisree
2 Replies
8. Solaris
There are two jobs in Solaris , Cron and at jobs..
I know how to disable or enable cron jobs.
How can I enable at jobs and disable it.
Kindly help.
Rj (2 Replies)
Discussion started by: jegaraman
2 Replies
9. Red Hat
I'm running cronjobs on a redhat 5.X. Cronjobs are getting failed frequently so how to find the root cause (2 Replies)
Discussion started by: karthik9358
2 Replies
10. Shell Programming and Scripting
How to see which cron jobs are not running? (2 Replies)
Discussion started by: rahul.raj1989
2 Replies
LEARN ABOUT HPUX
gss_unwrap
gss_unwrap(3) Library Functions Manual gss_unwrap(3)
NAME
gss_unwrap - verify a message with attached message integrity code (MIC) and decrypt message content if necessary
SYNOPSIS
DESCRIPTION
The routine converts a protected message to a usable form and verifies the embedded message integrity code (MIC). The conf_state parameter
indicates whether the message was encrypted. The qop_state parameter indicates the quality of protection that was used to provide the con-
fidentiality and integrity services.
Input Parameters
context_handle Specifies the context on which the message arrived.
input_message_buffer Specifies the protected message.
output_message_buffer Specifies the buffer to receive the unwrapped message.
Output Parameters
conf_state Returns the requested level of confidentiality and integrity services, as follows:
Non-zero Both confidentiality and integrity services were used.
zero Only integrity services was used.
qop_state Returns the cryptographic algorithm, or quality of protection.
minor_status Returns a status code from the security mechanism.
STATUS CODES
The following status codes can be returned:
The routine was completed successfully.
The signature was incorrect.
The context has already expired.
The context is recognized but the associated
credentials have expired.
The token failed consistency checks.
The token was valid and contained the correct
signature but it had already been processed.
The routine failed. The context specified in the context_handle parameter was not valid.
The context identified in the
context_handle parameter was not valid.
The token was valid and contained the correct signature
but it is too old.
The token was valid, and contained a correct MIC
for the message, but has been verified out of sequence; a later token has already been received.
The token was valid, and contained a correct MIC
for the message, but has been verified out of sequence; an earlier expected token has not yet been received.
AUTHOR
was developed by Sun Microsystems, Inc.
SEE ALSO
gss_get_mic(3), gss_wrap(3).
gss_unwrap(3)