not able to find one script
 

I got a mail today from my client as follows. What are the steps I should take to solve this problem?? please reply as soon as possible. Its urgent.

-------------------------------------------------------------------------


Each day one script running in CMS_UAT(Hostname os server) copies and renames branch file from CMS

This script does two following function

1) Copies the file named CMS_CRM_yyyymmddhhminsec_1 (exampleCMS_CRM_20110206194510_1)
from the K:\ReverseMigration\prod-dd-mm-yyyy-xls ( example K:\ReverseMigration\prod-06-02-2011-xls) to the folder Named backup/cms_crm)
2) It renames the file to CMS_CRM.CSV

This script is not running from the day CMS_UAT crashed and restored again.
Please start running the script at around 8pm every night

-----------------------------------------------------------------------
I am not able to find the script.

Look in the cron* directories.

Kind regards

First, this is NOT URGENT FOR ANYONE HERE. We volunteer our time, and answer when we want to, if we want to.

Second, you need to provide details when asking a question...things like version/distro of Linux, error(s) you're getting, what you're doing to get them, etc.

The script references a "K" drive...which is a WINDOWS drive letter. Linux doesn't use such things...have you tried to look on the Windows server for the batch file? Does this script touch a Linux server in any way? Any details about the script?? If it's a Windows script, you should try a Microsoft forum...this is LinuxQuestions....

I saw cron*. but no script is present

Ok...now how about answering the REST of the questions we asked?

- Is this a Linux script or Windows script?
- Which box does it run on?
- Is it a script or batch file?
- You say you "saw cron"...WHICH cron? The /etc/cron.*, or the ones in /var?

At least acknowledge the posts people make for you, and answer the questions that are asked.

The script could reside anywhere on the file system. So you should look in the earlier (prior to CMS_UAT crash and restore) copy of the scheduler files (cron in the case of linux) to see where the script file resides.

Otherwise, rewrite the script and stick it in. Seems simple enough.

End

thanx....its better to write again
 

thanx....its better to write again