Cause Analysis of SUSEcrontab tool failure

Article Title: Cause Analysis of SUSEcrontab tool failure. Linux is a technology channel of the IT lab in China. Includes basic categories such as desktop applications, Linux system management, kernel research, embedded systems, and open source.

I. SUSE crontab not executed:

When the crontab runs the program, it does not read the current user. Profile, solution --

1. If you have the root permission, you can modify crontab as follows:

7 50 *** su-user-c/channel/app/back/scripts/serv_cust.sh>/channel/app/cron. out

2. You can also add it to serv_cust.sh.

. $ HOME/. profile

To obtain. Various environment variables defined in profile

3. Permission issues may also occur. Method: common users must be listed in/etc/cron. allow (if the file exists) or not in/etc/cron. deny. Check whether the oracle user is in the preceding file.

4. You need to configure oracle environment parameters before executing the program, such as $ ORACLE_HOME;

Write a script file test. sh first.

#! /Bin/sh

ORACLE_HOME =/home/oracle

Export ORACLE_HOME

......

/Usr/users/oracle/test1

Then write the crontab script:

4 ***/usr/users/oracle/test. sh

You can.

No. Environment variables in profile

It may be an oracle environment variable.

2. Solve the Problem of solaris crontab not executing

1. First kill/usr/sbin/cron. You can use ps-ef | grep cron to get the ID number.

2. rm/etc/cron. d/fifo

3./usr/sbin/cron