06-24-2010
BINGO ! its working after export.
Thanks all for the help.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I have a backup script that is suppose to run every night of the week, but it never does, it starts to run. The way I can tell is that the dates on dump_log are changing to when the script runs. If I look in the cron log file is shows
! > root 506342 cr /etc/back_up Fri Aug 5 10:30:00... (2 Replies)
Discussion started by: rickyt00
2 Replies
2. HP-UX
Dear Folks,
i am new to hp-ux, i have a problem scheduling the crontab,
The script is working fine at command prompt, but not working at cron, please find a solution for it ,
here are the logs and my schedule at cron:
log after restarting crontab /var/adm/cron/log
! *** cron started *** ... (11 Replies)
Discussion started by: vaddi
11 Replies
3. UNIX for Advanced & Expert Users
I am adding a piece of code which adds entry in crontab ((in brown color))
\crontab -l > $tmpfile
echo "Removing the cleanProcess entry if it already existed.."
grep -v "cleanProcess.sh" $tmpfile > $newtmpfile
lcnt=`grep -c "cleanProcess.sh" $tmpfile`
echo... (4 Replies)
Discussion started by: crackthehit007
4 Replies
4. Shell Programming and Scripting
Helo .
I have 2.6.13-1.1526_FC4smp here.
I am trying to make crontab execute my simple shell script, but noting happens.
here is how i am testing this :
$ pwd
/home/oracle
$ ls -l two*
ls: two*: No such file or directory
$
$ crontab -e
crontab: installing new crontab
$
$ crontab... (7 Replies)
Discussion started by: tonijel
7 Replies
5. UNIX for Advanced & Expert Users
We have configured a script to be run at specific time using crontab.
# crontab -l
15 11 * * * VM_Count_V4.shas per the crontab entry script should run every day 11.15 a.m
Every time when the script is executed i get a mail but when i run it using crontab it doesn't send any mail.
However... (1 Reply)
Discussion started by: pinga123
1 Replies
6. AIX
Hi all,
I'm having a problem with a crontab entry execution for a non root user.
AIX version 5.3
user@host ~ $ oslevel -r
5300-10
cron status
user@host ~ $ ps -ef | grep cron
root 377044 1 0 Oct 27 - 0:22 /usr/sbin/cron
cron entry for user
user@host ~ $... (3 Replies)
Discussion started by: h@foorsa.biz
3 Replies
7. UNIX for Dummies Questions & Answers
Hi,
I have a cronjob but it is not getting executed.Is there any ways to check whether crontab is working.I have put crontab -l and checked.It got listed.But it is not working.
My Crontab is,
* * * * * /ldesk/home/abc/source/compare.sh >/dev/null 2>&1 (1 Reply)
Discussion started by: gayisada
1 Replies
8. Shell Programming and Scripting
hi,
i have schduled a job through crontab, but it is not getting executed.
bash-3.2$ crontab -l
# Monthly Download (mm hh DD MM format)
35 05 01 04 * /home/ftpsrp/srpftp1/download/ofrdb/scripts/load_ofrdb.sh crr.sh
here is the permission of the .sh files
-rwxr--r-- 1 ftpsrp srp ... (7 Replies)
Discussion started by: lovelysethii
7 Replies
9. UNIX for Advanced & Expert Users
My colleague who was a sysadmin , has created a cron job script which collects logs and process them.
The script works perfectly as per the defined time set by him.
it works when we keep the timing as 55 05 * * * , whereas if we try to prepone the cron task is not getting executed.
Where... (10 Replies)
Discussion started by: aravindj80
10 Replies
10. UNIX for Dummies Questions & Answers
Hello,
I have a bash script that finds files older than 31 days and deletes them. I have this file loading into crontab to run everyday. It ran fine the first time i loaded it in, but now when I try to run it manually (bash file.sh) I get errors.
Here is the script
TIME=" -maxdepth 1... (6 Replies)
Discussion started by: jrymer
6 Replies
LEARN ABOUT OSX
git-cvsexportcommit
GIT-CVSEXPORTCOMMIT(1) Git Manual GIT-CVSEXPORTCOMMIT(1)
NAME
git-cvsexportcommit - Export a single commit to a CVS checkout
SYNOPSIS
git cvsexportcommit [-h] [-u] [-v] [-c] [-P] [-p] [-a] [-d cvsroot]
[-w cvsworkdir] [-W] [-f] [-m msgprefix] [PARENTCOMMIT] COMMITID
DESCRIPTION
Exports a commit from GIT to a CVS checkout, making it easier to merge patches from a git repository into a CVS repository.
Specify the name of a CVS checkout using the -w switch or execute it from the root of the CVS working copy. In the latter case GIT_DIR must
be defined. See examples below.
It does its best to do the safe thing, it will check that the files are unchanged and up to date in the CVS checkout, and it will not
autocommit by default.
Supports file additions, removals, and commits that affect binary files.
If the commit is a merge commit, you must tell git cvsexportcommit what parent the changeset should be done against.
OPTIONS
-c
Commit automatically if the patch applied cleanly. It will not commit if any hunks fail to apply or there were other problems.
-p
Be pedantic (paranoid) when applying patches. Invokes patch with --fuzz=0
-a
Add authorship information. Adds Author line, and Committer (if different from Author) to the message.
-d
Set an alternative CVSROOT to use. This corresponds to the CVS -d parameter. Usually users will not want to set this, except if using
CVS in an asymmetric fashion.
-f
Force the merge even if the files are not up to date.
-P
Force the parent commit, even if it is not a direct parent.
-m
Prepend the commit message with the provided prefix. Useful for patch series and the like.
-u
Update affected files from CVS repository before attempting export.
-k
Reverse CVS keyword expansion (e.g. $Revision: 1.2.3.4$ becomes $Revision$) in working CVS checkout before applying patch.
-w
Specify the location of the CVS checkout to use for the export. This option does not require GIT_DIR to be set before execution if the
current directory is within a git repository. The default is the value of cvsexportcommit.cvsdir.
-W
Tell cvsexportcommit that the current working directory is not only a Git checkout, but also the CVS checkout. Therefore, Git will
reset the working directory to the parent commit before proceeding.
-v
Verbose.
CONFIGURATION
cvsexportcommit.cvsdir
The default location of the CVS checkout to use for the export.
EXAMPLES
Merge one patch into CVS
$ export GIT_DIR=~/project/.git
$ cd ~/project_cvs_checkout
$ git cvsexportcommit -v <commit-sha1>
$ cvs commit -F .msg <files>
Merge one patch into CVS (-c and -w options). The working directory is within the Git Repo
$ git cvsexportcommit -v -c -w ~/project_cvs_checkout <commit-sha1>
Merge pending patches into CVS automatically -- only if you really know what you are doing
$ export GIT_DIR=~/project/.git
$ cd ~/project_cvs_checkout
$ git cherry cvshead myhead | sed -n 's/^+ //p' | xargs -l1 git cvsexportcommit -c -p -v
GIT
Part of the git(1) suite
Git 1.7.10.4 11/24/2012 GIT-CVSEXPORTCOMMIT(1)