Continuous nc data acquisition fails ocassionally Post: 303018293

5 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Need info regarding CDP - continuous data protection

HI frnds, i am going to work on CDP(continuous data protection),does any one of them have any idea reg CDP ... any docs or Links...might be helpful to me in understanding it....

2. Shell Programming and Scripting

Continuous checking of a file

I have a requirement like this... I want to go to a particular server for which i have acess .I want to do a ssh to that server from one server and check if a file is theer or not..and i need the script to chcek continuosly till it finds the file.When it finds the file i want it to come out...

3. UNIX for Dummies Questions & Answers

Extracting data between continuous non empty xml tags

Hi, I need help in extracting only the phone numbers between the continuous non empty xml tags in unix. I searched through a lot of forum but i did not get exact result for my query. Please help Given below is the sample pipe delimited file. I have a lot of tags before and after...

4. Shell Programming and Scripting

Continuous Copying from a directory to another.

Hello Folks, Looking for a script, where i can check for the existing of the files in a directory and copying to another. How can i achieve it in loop for over period of time. whatever files comes into the folder copied in another without duplicate and should be continuous loop. ...

5. UNIX for Beginners Questions & Answers

Continuous for loop

Hi All, Please help ***************** a=100 and run for loop that will minus 30 from 100 an will display value run loop will run till display value will be 0 ***************** Thanking you

LEARN ABOUT OSF1

cron

cron(8) 						      System Manager's Manual							   cron(8)

NAME

       cron - The system clock daemon

SYNOPSIS

       /usr/sbin/cron

DESCRIPTION

       The cron daemon runs shell commands at specified dates and times.  Commands that are to run according to a regular or periodic schedule are
       found within the crontab files.	Commands that are to run once only are found within the at files.  You submit crontab and at file  entries
       by  using  the  crontab	and  at  commands.  Because the cron process exits only when killed or when the system stops, only one cron daemon
       should exist on the system at any given time.  Normally, you start the cron daemon from within a run command file.

       During process initialization and when cron detects a change, it examines the crontab and at files.  This strategy reduces the overhead	of
       checking  for  new  or  changed files at regularly scheduled intervals.	The cron command creates a log of its activities.  The cron daemon
       must be started from the system startup scripts because it must begin execution without a login user ID set.  The cron daemon  starts  each
       job  with the following process attributes stored with the job by the invoking process: Login user ID Effective and real user IDs Effective
       and real group IDs Supplementary groups

       It also establishes the following attributes from the authentication profile of the account associated with the login user ID of the invok-
       ing process: Audit control and disposition masks Kernel authorizations

DIAGNOSTICS

       The at and batch programs will refuse to accept jobs submitted from processes whose login user ID is different from the real user ID.

FILES

       Specifies the command path.  Main cron directory Directory containing the crontab files.  List of allowed users.  List of denied users His-
       tory information for cron Queue description file for at, batch, and cron

RELATED INFORMATION

       Commands:  at(1), crontab(1), rc0(8), rc2(8), rc3(8)

       Files: queuedefs(4) delim off

																	   cron(8)