Sponsored Content
Operating Systems Solaris please review this cron syntax Post 302325777 by jayan_jay on Tuesday 16th of June 2009 06:25:41 AM
Old 06-16-2009
0 6 * * 6 cd /export/home/jenova ; ls -ltr >> $HOME/jenova_dir
 

5 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Can someone review my code tell me where I am going wrong?

Started writing my code. my read input is not even asking nor working? And I get a EOF script error. echo "1) aragorn.domain.net" echo "2) marvel.domain.net" echo "3) athena.domain.net" echo "4) gandalf.domain.net" echo "5) griffin.domain.net" echo "What server would you like... (4 Replies)
Discussion started by: chrchcol
4 Replies

2. Shell Programming and Scripting

Please, review script.

Hi guys, I 've been brewing this shellscript, but I can't test it until next tuesday. In the meantime I am too curious wether it will work or not, so I'd like to hear your comments. Background: I want to watch the user quota for mailboxes in various email-domains on a IMAP-server. I have... (1 Reply)
Discussion started by: algernonz
1 Replies

3. Cybersecurity

Log Review- SU

Hi, Can some please provide some hints on what to look for in unix/Linux logs such as sulog from a Information security perspective. Regards (2 Replies)
Discussion started by: Tilus
2 Replies

4. UNIX for Advanced & Expert Users

Command syntax error in cron

SCO OSR 507, user's shell is old Bourne sh The same command is OK when run using now, but fails when run in cron, see below: 1) using now, see how it worked and I see resulting DT=2018 in the mail $ at now { dt=`/usr/gnu/bin/date '+%Y'`; echo "DT=$dt"; } job 1522867418.a-6605:0 at Wed... (2 Replies)
Discussion started by: migurus
2 Replies

5. Shell Programming and Scripting

(standard_in)1:syntax error using bc with Cron

I created a shell script to record server temperature. When I manually run script it works fine with no error message. But when I create a cron job, my script fails with error message (standard_in)1:syntax error. I figured out the bc utility is causing the error message. Below is my script. ... (7 Replies)
Discussion started by: SysAdminRialto
7 Replies
EXPORT(3PVM)															      EXPORT(3PVM)

NAME
pvm_export, pvm_unexport - Mark environment variables to export through spawn SYNOPSIS
C int cc = pvm_export( char *name ) int cc = pvm_unexport( char *name ) Fortran Not available PARAMETERS
name Name of an environment variable to add to or delete from export list. DESCRIPTION
The routines pvm_export and pvm_unexport are provided for convenience in editing environment variable PVM_EXPORT, while maintaining the colon-separated list syntax it requires. The variable can be modified by other means, and at the same time by the pvm_export functions. pvm_export checks to see if a name is already in PVM_EXPORT before including it, and exporting a name more than once is not considered an error. Likewise, pvm_unexport will not complain if you specify a name not in PVM_EXPORT. EXAMPLES
C: /* PVM_EXPORT=SHELL:HOME */ pvm_export("DISPLAY"); pvm_export("TERM"); pvm_unexport("HOME"); /* PVM_EXPORT=SHELL:DISPLAY:TERM */ ERRORS
No error conditions are currently returned by pvm_export and pvm_unexport. SEE ALSO
pvm(1PVM) pvm_spawn(3PVM) 15 May, 1996 EXPORT(3PVM)
All times are GMT -4. The time now is 03:53 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy