Strange behaviour from script in crontab Post: 302209253

9 More Discussions You Might Find Interesting

1. Linux

/etc/passwd strange behaviour!

Hi there, first of all, here is my conf of a uname -a Linux SAMBA 2.4.18-4GB #1 Wed Mar 27 13:57:05 UTC 2002 i686 unknown on a fedora machine. Here is my problem: every once in a while, the line containing root disappears in the /etc/passwd, disabling all logging on my server. Any one have...

2. Shell Programming and Scripting

A Strange Behaviour!!!

Can some-one give me a view to this : I have a directory in an unix server, having permissions r-xr-xr-x .This directory is basically a source directory. Now there is another directory basically the destination directory which has all the permissions. Note:I log in as not the owner,but user...

3. Shell Programming and Scripting

strange behaviour from sed???

Hi all, I want to do a very simple thing with sed. I want to print out the line number of a disk I have defined in /etc/exports, so I do: It's all good, but here's the problem. When I define md0 in a variable, I get nothing from sed: Why is that? can anybody please help? Thanks

4. Shell Programming and Scripting

Expect script strange behaviour

Hi people, I'm having some strange behaviour with an 'expect' script. spawn csession blah expect "Username: " send "userblah\r" expect "Password: " send "passwordblah\r" interact When I execute the script as root it runs perfectly. However, when executed as any other...

5. Shell Programming and Scripting

Strange behaviour with perl i/o?

Hi All, I got a strange problem here. I have a perl script which is fetching data from a database table and writing a file with that data. If i run that script from linux command line, the file it creates is a normal ascii text file without any binary character in it.But...

6. Shell Programming and Scripting

Strange RegExp Behaviour

Hello, I was trying to identify lines who has a word of the following pattern "xyyx" (where x, and ys are different characters). I was trying the following grep - egrep '(\S)()\2\1' This pattern do catches the wanted pattern, but it also catches "GGGG" or "CCCC" patterns. I was trying to...

7. Red Hat

Crontab strange behaviour

Hi all, I'm having this scenario which for the moment I cannot resolve. :( I wrote a script to make a dump/export of the oracle database. and then put this entry on crontab to be executed daily for example. The script is like below: cat /home/oracle/scripts/db_backup.sh #!/bin/ksh ...

8. Shell Programming and Scripting

strange behaviour script terminate before complete execution

I'm working on a script to make backup of various folder located on various host using different OS. I got a strange behaviour because the script don�t process all lines of a configuration file, the script execute only one loop even the input file have 6 lines: This is the script: #!/bin/bash...

9. Shell Programming and Scripting

Strange Script behaviour with Grep

Here is my script LOGDATE=`date '+%Y-%m-%d %k:%M' | cut -c1-15` echo $LOGDATE echo "grep '$LOGDATE' /tmp/logs/vel.log >10min_log" grep '$LOGDATE' /tmp/logs/vel.log>10min_log grep '$LOGDATE' /tmp/logs/vel.logHere is the output of the script -rw-r--r-- 1 wluser wluser 0 May 3...

LEARN ABOUT SUSE

crontab

CRONTAB(1)						      General Commands Manual							CRONTAB(1)

NAME

       crontab - maintain crontab files for individual users (ISC Cron V4.1)

SYNOPSIS

       crontab [-u user] file
       crontab [-u user] [-l | -r | -e]

DESCRIPTION

       Crontab	is  the  program  used	to install, deinstall or list the tables used to drive the cron(8) daemon in ISC Cron.	Each user can have
       their own crontab, and though these are files in /var, they are not intended to be edited directly.

       If the cron.allow file exists, then you must be listed therein in order to be allowed to use this command.  If the cron.allow file does not
       exist  but  the	cron.deny  file does exist, then you must not be listed in the cron.deny file in order to use this command.  If neither of
       these files exists, only the super user will be allowed to use this command.

       If the -u option is given, it specifies the name of the user whose crontab is to be tweaked.  If this option is not given, crontab examines
       "your"  crontab,  i.e.,	the  crontab of the person executing the command.  Note that su(8) can confuse crontab and that if you are running
       inside of su(8) you should always use the -u option for safety's sake.

       The first form of this command is used to install a new crontab from some named file or standard input  if  the	pseudo-filename  ``-''	is
       given.

       The -l option causes the current crontab to be displayed on standard output.

       The -r option causes the current crontab to be removed.

       The -e option is used to edit the current crontab using the editor specified by the VISUAL or EDITOR environment variables.  After you exit
       from the editor, the modified crontab will be installed automatically.

SEE ALSO

       crontab(5), cron(8)

FILES

       /etc/cron.allow
       /etc/cron.deny

STANDARDS

       The crontab command conforms to IEEE Std1003.2-1992 (``POSIX'').  This new command syntax differs from previous versions of Vixie Cron,	as
       well as from the classic SVR3 syntax.

DIAGNOSTICS

       A fairly informative usage message appears if you run it with a bad command line.

AUTHOR

       Paul Vixie <vixie@isc.org>

4th Berkeley Distribution					 29 December 1993							CRONTAB(1)