Sponsored Content
Top Forums UNIX for Advanced & Expert Users [Tip] How to add an application cron job? Post 302871195 by bakunin on Tuesday 5th of November 2013 04:10:45 PM
Old 11-05-2013
Very good tip. Thank you.

I have added "[Tip]" in the title to make it easier to find it.

bakunin
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Graph application tip request

Hi, as a Mac OS X user I am not into Unix at all. But since it is possible to run Unix application on Mac I am specialy interested in a program making scientifical graphs. There is SigmaPlot for WIN PC´s and this is more or less what I would like to use. So, here comes the question: is there a... (3 Replies)
Discussion started by: zwen
3 Replies

2. Solaris

cron job starts new cron proccess

I run cron in solaris 10 zone. One cron job which syncing files to nfs mounted on container, creates after finishing another cron proccess(/usr/sbin/cron), and after 100 existing cron proccesses next cron job will not start. It's too weird for me, I'm not able to solve this problem. Theoretically... (3 Replies)
Discussion started by: ron76
3 Replies

3. Shell Programming and Scripting

How to add cron job in /etc/crontab

Hi, How to add a cron job in /etc/crontab using a shell script.??:confused: Actually the requirement is we need to run a script say, XXX.sh every 10 min through “cron”. That can be achieved by adding the below code line in the /etc/crontab , (i.e., “crontab -e ” command to add this to the... (4 Replies)
Discussion started by: Dedeepthi
4 Replies

4. Solaris

Cron job running even after cron is removed

Hi , I have removed a cron for particular user , but cron job seems to be running even after the cron entry is removed. The purpose of the cron was to sendmail to user ( it uses mailx utility ) I have restarted cron and sendmail service still user is getting mail alerts from the cron job. And... (4 Replies)
Discussion started by: chidori
4 Replies

5. Shell Programming and Scripting

Commented cron job -- cron monitoring

Hi I have a requirement to write a shell script,that will check the all commented job in cron job.Please help !! (2 Replies)
Discussion started by: netdbaind
2 Replies

6. UNIX for Advanced & Expert Users

[Tip] How to add individual delays to a cron job?

ofIn a big Unix environment you likely install cron jobs like this on a thousand systems: 39 15 * * * { /usr/local/monitoring/sendstats ; } >/dev/null 2>&1If all the system clocks are synchronized (usually via NTP), these jobs run *exactly* at the same time. If the cron job accesses a shared... (2 Replies)
Discussion started by: MadeInGermany
2 Replies

7. Shell Programming and Scripting

Cron job - Need to run Cron every quarter at particular time

Hi, 1) If some job supposed to run on 1st of every month at 7 AM In cron job when we have a blackout on the 1st ( i.e when 1st falls on a sunday ) how can we make the job run the next business day? 2) How can we run a job on 25th of every quarter 7 AM(jan,apr,jul,oct) And if 25th... (5 Replies)
Discussion started by: System Admin 77
5 Replies

8. UNIX for Beginners Questions & Answers

Add TimeStamp to cron job and write file name sent

Hello, I have written a cron job to automate the sftp of files using key authentication. I wanted to add a timeStamp and name of file sent to a log file and append each these details to the same file each time files are sent and if possible include whether the files were sent successfully or not.... (3 Replies)
Discussion started by: KidKoder
3 Replies

9. UNIX for Advanced & Expert Users

Tip: inotify cron

Dear members, moderators and others. While working on <insert project>, a need has surfaced to watch a directory, and when a file comes, to do appropriate action. So, i started writing some shell code, aware of linux inotify-tools package with inotifywait. Also, i'm seeing a lot of similar... (1 Reply)
Discussion started by: Peasant
1 Replies
TIP(1C) 																   TIP(1C)

NAME
tip, cu - connect to a remote system SYNOPSIS
tip [ -v ] [ -speed ] system-name tip [ -v ] [ -speed ] phone-number cu phone-number [ -t ] [ -s speed ] [ -a acu ] [ -l line ] [ -# ] DESCRIPTION
Tip and cu establish a full-duplex connection to another machine, giving the appearance of being logged in directly on the remote cpu. It goes without saying that you must have a login on the machine (or equivalent) to which you wish to connect. The preferred interface is tip. The cu interface is included for those people attached to the ``call UNIX'' command of version 7. This manual page describes only tip. Typed characters are normally transmitted directly to the remote machine (which does the echoing as well). A tilde (`~') appearing as the first character of a line is an escape signal; the following are recognized: ~^D ~. Drop the connection and exit (you may still be logged in on the remote machine). ~c [name] Change directory to name (no argument implies change to your home directory). ~! Escape to a shell (exiting the shell will return you to tip). ~> Copy file from local to remote. Tip prompts for the name of a local file to transmit. ~< Copy file from remote to local. Tip prompts first for the name of the file to be sent, then for a command to be executed on the remote machine. ~p from [ to ] Send a file to a remote UNIX host. The put command causes the remote UNIX system to run the command string ``cat > 'to''', while tip sends it the ``from'' file. If the ``to'' file isn't specified the ``from'' file name is used. This command is actually a UNIX specific version of the ``~>'' command. ~t from [ to ] Take a file from a remote UNIX host. As in the put command the ``to'' file defaults to the ``from'' file name if it isn't speci- fied. The remote host executes the command string ``cat 'from';echo ^A'' to send the file to tip. ~| Pipe the output from a remote command to a local UNIX process. The command string sent to the local UNIX system is processed by the shell. ~$ Pipe the output from a local UNIX process to the remote host. The command string sent to the local UNIX system is processed by the shell. ~# Send a BREAK to the remote system. For systems which don't support the necessary ioctl call the break is simulated by a sequence of line speed changes and DEL characters. ~s Set a variable (see the discussion below). ~^Z Stop tip (only available with job control). ~^Y Stop only the ``local side'' of tip (only available with job control); the ``remote side'' of tip, the side that displays output from the remote host, is left running. ~? Get a summary of the tilde escapes Tip uses the file /etc/remote to find how to reach a particular system and to find out how it should operate while talking to the system; refer to remote(5) for a full description. Each system has a default baud rate with which to establish a connection. If this value is not suitable, the baud rate to be used may be specified on the command line, e.g. ``tip -300 mds''. When tip establishes a connection it sends out a connection message to the remote system; the default value, if any, is defined in /etc/remote. When tip prompts for an argument (e.g. during setup of a file transfer) the line typed may be edited with the standard erase and kill char- acters. A null line in response to a prompt, or an interrupt, will abort the dialogue and return you to the remote machine. Tip guards against multiple users connecting to a remote system by opening modems and terminal lines with exclusive access, and by honoring the locking protocol used by uucp(1C). During file transfers tip provides a running count of the number of lines transferred. When using the ~> and ~< commands, the ``eofread'' and ``eofwrite'' variables are used to recognize end-of-file when reading, and specify end-of-file when writing (see below). File trans- fers normally depend on tandem mode for flow control. If the remote system does not support tandem mode, ``echocheck'' may be set to indi- cate tip should synchronize with the remote system on the echo of each transmitted character. When tip must dial a phone number to connect to a system it will print various messages indicating its actions. Tip supports the DEC DN-11 and Racal-Vadic 831 auto-call-units; the DEC DF02 and DF03, Ventel 212+, Racal-Vadic 3451, and Bizcomp 1031 and 1032 integral call unit/modems. VARIABLES Tip maintains a set of variables which control its operation. Some of these variable are read-only to normal users (root is allowed to change anything of interest). Variables may be displayed and set through the ``s'' escape. The syntax for variables is patterned after vi(1) and Mail(1). Supplying ``all'' as an argument to the set command displays all variables readable by the user. Alternatively, the user may request display of a particular variable by attaching a `?' to the end. For example ``escape?'' displays the current escape character. Variables are numeric, string, character, or boolean values. Boolean variables are set merely by specifying their name; they may be reset by prepending a `!' to the name. Other variable types are set by concatenating an `=' and the value. The entire assignment must not have any blanks in it. A single set command may be used to interrogate as well as set a number of variables. Variables may be initialized at run time by placing set commands (without the ``~s'' prefix in a file .tiprc in one's home directory). The -v option causes tip to display the sets as they are made. Certain common variables have abbreviations. The following is a list of common variables, their abbreviations, and their default values. beautify (bool) Discard unprintable characters when a session is being scripted; abbreviated be. baudrate (num) The baud rate at which the connection was established; abbreviated ba. dialtimeout (num) When dialing a phone number, the time (in seconds) to wait for a connection to be established; abbreviated dial. echocheck (bool) Synchronize with the remote host during file transfer by waiting for the echo of the last character transmitted; default is off. eofread (str) The set of characters which signify and end-of-tranmission during a ~< file transfer command; abbreviated eofr. eofwrite (str) The string sent to indicate end-of-transmission during a ~> file transfer command; abbreviated eofw. eol (str) The set of characters which indicate an end-of-line. Tip will recognize escape characters only after an end-of-line. escape (char) The command prefix (escape) character; abbreviated es; default value is `~'. exceptions (str) The set of characters which should not be discarded due to the beautification switch; abbreviated ex; default value is `` f''. force (char) The character used to force literal data transmission; abbreviated fo; default value is `^P'. framesize (num) The amount of data (in bytes) to buffer between file system writes when receiving files; abbreviated fr. host (str) The name of the host to which you are connected; abbreviated ho. prompt (char) The character which indicates and end-of-line on the remote host; abbreviated pr; default value is ` '. This value is used to synchronize during data transfers. The count of lines transferred during a file transfer command is based on recipt of this character. raise (bool) Upper case mapping mode; abbreviated ra; default value is off. When this mode is enabled, all lower case letters will be mapped to upper case by tip for transmission to the remote machine. raisechar (char) The input character used to toggle upper case mapping mode; abbreviated rc; default value is `^A'. record (str) The name of the file in which a session script is recorded; abbreviated rec; default value is ``tip.record''. script (bool) Session scripting mode; abbreviated sc; default is off. When script is true, tip will record everything transmitted by the remote machine in the script record file specified in record. If the beautify switch is on, only printable ASCII characters will be included in the script file (those characters betwee 040 and 0177). The variable exceptions is used to indicate characters which are an exception to the normal beautification rules. tabexpand (bool) Expand tabs to spaces during file transfers; abbreviated tab; default value is false. Each tab is expanded to 8 spaces. verbose (bool) Verbose mode; abbreviated verb; default is true. When verbose mode is enabled, tip prints messages while dialing, shows the current number of lines transferred during a file transfer operations, and more. SHELL (str) The name of the shell to use for the ~! command; default value is ``/bin/sh'', or taken from the environment. HOME (str) The home directory to use for the ~c command; default value is taken from the environment. FILES
/etc/remote global system descriptions /etc/phones global phone number data base ${REMOTE} private system descriptions ${PHONES} private phone numbers ~/.tiprc initialization file. /usr/spool/uucp/LCK..* lock file to avoid conflicts with uucp DIAGNOSTICS
Diagnostics are, hopefully, self explanatory. SEE ALSO
remote(5), phones(5) BUGS
The full set of variables is undocumented and should, probably, be paired down. 4th Berkeley Distribution May 5, 1986 TIP(1C)
All times are GMT -4. The time now is 07:40 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy