Solaris

No Kishore, there is no change after trying this.

Note:
Whenever I am closing the session after using the crontab -e. I am getting this message all the time

$ exit
You have stopped jobs

But If i doesnt use crontab -e I wont be getting any this type of message while closing the session.

Any point to concentrate on this ????

Could you please describe exactly everything you are doing, please?
I mean, steps, commands, user, shell, etc... from the begining, when you login, to the end, when you exit.

Hi grial,

Please go through the steps I have done.

login: oracle10
Password:

$ oraenv
ORACLE_SID = [gdbuat] ? gdbuat

$ crontab -l
03 12 * * * /gdbuat4/backupscripts/dailyexp10g.sh >> /tmp/export.log

$ crontab -e (AS THE VI EDITOR IS NOT OPENING WHILE ISSUING crontab -e I CLOSED USING CTRL+Z)
137
^Z[2] + Stopped (SIGTSTP) crontab -e


$ export EDITOR=vi
$

$crontab -e ----------Replacing the old one with new.
00 00 * * 6 /gdbuat4/backupscripts/weeklyexp10g.sh >> /tmp/export.log

$ crontab -l
00 00 * * 6 /gdbuat4/backupscripts/weeklyexp10g.sh >> /tmp/export.log

$ exit
You have stopped jobs

$ exit


OPENING NEW SESSION:

login: oracle10
Password:

$ oraenv
ORACLE_SID = [gdbuat] ? gdbuat

$ crontab -l
03 12 * * * /gdbuat4/backupscripts/dailyexp10g.sh >> /tmp/export.log

I cant see the changes What ever I made in crontab entry in the old session.

If any questions please revert back to me.

Regards,
Prashanth

Why did you give CTRL-Z? That does not end the "crontab -e" process. That's why the "Stopped (SIGTSTP) crontab -e" and "You have stopped jobs" messages are displayed.

First of all, check whether there is any crontab commad running:

Code:

ps -ef | grep oracle10 | grep crontab | grep -v grep

- kill it/them.
- Set the appropriate EDITOR value in your shell initialization file. Exit and login again.
- "crontab -e"
- make changes, save them and exit.
- login and let's see...

Yep..Prashanth

Grial is perfect..!!!!!!!Thanks a lot grial.

We'll wait for the heads up!!!!!!!!!!!

Thanks
Kishor

SESSION 1:

$ ps -ef | grep oracle10 | grep crontab | grep -v grep

$kill -9 22754
$kill -9 22755
$kill -9 22747

(I killed all the crontab session )

$ps -ef | grep oracle10 | grep crontab | grep -v grep

$export EDITOR=vi

$crontab -e

00 00 * * 6 /gdbuat4/backupscripts/weeklyexp10g.sh >> /tmp/export.log


$ crontab -l
00 00 * * 6 /gdbuat4/backupscripts/weeklyexp10g.sh >> /tmp/export.log

OPENED NEW SESSION (SESSION 2), I HAVENT CLOSED (SESSION 1)

login: oracle10
Password:

$ oraenv
ORACLE_SID = [gdbuat] ? gdbuat

$ crontab -l
00 00 * * 6 /gdbuat4/backupscripts/weeklyexp10g.sh >> /tmp/export.log

NOW CLOSED THE SESSION 1

$ exit
You have stopped jobs

$ exit

NOW IN SESSION 2

$ crontab -l
03 12 * * * /gdbuat4/backupscripts/dailyexp10g.sh >> /tmp/export.log
35 15 * * * /gdbuat4/backupscripts/sample.sh >> /tmp/export1.log

Conclusion:

If I close the session 1 where I have made changes in the crontab entry, the changes get removed while validating in Session 2. If not closed
Session 2 shows the updated entry.

Its really strange.

Hope you got the point.

Please explain.

Prashanth

Just see the stopped jobs by typing the command

fg

i.e dat jobs will come up in foreground


Thanks
Kishor