UNIX for Dummies Questions & Answers

Thanks for your replies guys,

I can NOT log in, using THAT password. But I can LOG IN switching from the root user with 'su - oracle'. If THAT is the password as you said and the password expired , isn't strange that I can switch from the root account?
This is the only way that I can use the oracle account, and it is working fine.

Thanks again.

su'ing from root will always work since no password
is required. From root, you can change the orecle user password

# passwd oracle

Yes, but as the password is no longer valid for that user shouldn't be nice to have a warning or something?
The thing is that even the account is inactive logs me in like this:
and all the functions are working. If this is the case, then I only need to reset the password and the crontab will run fine, correct?

<pre>

isgsi01(root)9: su - oracle
Sun Microsystems Inc. SunOS 5.7 Generic October 1998
$ whoami
oracle

</pre>

Well... "root" is GOD on most (if not all) flavors of UNIX
so you can pretty much do anything and you woun't
get much if any warnings.

I assume that if oracle's cron job is not running
because of an expired password then reseting it may in
fact work however I have not actually tried this.

I say... give it a shot.

1. Run the cron from root and not from oracle
2. prefix su -c oracle to the script that you want to run in cron

this will actually run the cronjob as root by su it to oracle before running the script.

hope this would help you.

we are doing exactly the same on our systems.

Milind.

Hi

------------------------------------------------------------------------------------
CRONTAB USAGE : For Using "crontab" utility to Edit Cron Files
using Vi as the Editor, perform the below mentioned Steps.

# EDITOR=vi; export EDITOR;
# crontab -e <username>

U will get a Vi Editor Screen for editing the mentioned User's Cron File. { Only use this way to edit any Cron File, as directly editing the Cron files might corrupt the File }

------------------------------------------------------------------------------------
CRONTAB TROUBLESHOOTING : If Ur Cronjob is not getting executed correctly, Then check for the below mentioned....

1. Check for the Permissions of the Cron File and Syntax of its contents.

# ls -l /var/spool/cron/crontabs/
total 4
-r-------- 1 root other 310 Mar 31 12:50 backup_user
-r-------- 1 root root 424 Feb 21 21:41 root

2. Check the UserName Entries present in the below mentioned Files.

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

3. Check whether Daemon for Cron is running or not.

# ps -ef |grep cron |grep -v grep
root 183 1 0 Mar 28 ? 0:03 /usr/sbin/cron

4. If the Daemon is not running, Restart the Daemon as mentioned below

# /etc/init.d/cron stop
# /etc/init.d/cron start

5. If U are executing any customised Shell Scripts using Cron,
then U have to check whether proper Execute Permissions are
provided for that Cron User.

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

If U still face any problem, Kindly get back with Proper Error Messages updated in the /var/adm/messages File.