08-30-2011
Unable to open Crontab
Hi,
I have 2 solaris server. I can able to open to see cron entry by using crontab -l in one of the server. I cant able to open another server. How to check if crontab is fixed in that server. If not then how to make a crontab in that server.
Please advice.
Thanks,
Mani
---------- Post updated at 04:05 AM ---------- Previous update was at 12:12 AM ----------
Thanks to all. I have solved this issue. There is no entry in /etc/cron.d/cron.allow file. So i cant able to open . It will be help for some one
Thanks,
Mani
9 More Discussions You Might Find Interesting
1. Post Here to Contact Site Administrators and Moderators
I am unable to open the mimesender thread. I get the following message when clicking on https://www.unix.com/showthread.php?p=33233#post33233 : (2 Replies)
Discussion started by: dangral
2 Replies
2. UNIX for Dummies Questions & Answers
I am a dba, not an sa, that recently had to take over administering an HP-UX server. Needless to say I am not in a comfortable area, but found out that of all people I am the most knowledgeable on unix here .... scary thought I know.
I am having troubles exporting my display to a Windows XP... (5 Replies)
Discussion started by: soestx
5 Replies
3. Solaris
Hi Everyone,
Each time I do update the crontab, it gets reset after exiting from the telnet session. I'm using Solaris 2.8
So it goes like this:
Step 1: Login as root, from a telnet session
Step 2: Crontab -e (I make modification)
Step 3: Save and exit
Step 4: Type crontab -l , changes... (4 Replies)
Discussion started by: Jeremy3
4 Replies
4. Post Here to Contact Site Administrators and Moderators
Hi,
I am unable to view/open the image I uploded in one of the forums.
https://www.unix.com/showthread.php?t=37793&page=2&pp=20
Please help.
enc. (2 Replies)
Discussion started by: encrypted
2 Replies
5. UNIX for Dummies Questions & Answers
Hi ,
I am running Oracle 8.1.7 on HP-UX B.11.00. Recently I have upgraded Oracle from 8.0.6. to 8.1.7. Almost all the shell script has the Sqlplus as sqlplus -s @/apps/prod/sql/xxxx.sql > /apps/prod/log/xxxx.out .
However I receive the error
SP2-0310: unable to open file... (2 Replies)
Discussion started by: Ananth.p
2 Replies
6. UNIX for Advanced & Expert Users
Hi,
I unable to open any file using Vi editor,constantly getting the following error,
vi log.log
*** glibc detected *** malloc(): memory corruption: 0x081af510 **
uname -a
Linux sekac092 2.6.5-7.244-bigsmp #1 SMP Mon Dec 12 18:32:25 UTC 2005 i686 athlon i386 GNU/Linux
Also Note
ls... (8 Replies)
Discussion started by: ennstate
8 Replies
7. UNIX for Advanced & Expert Users
I am working on a unix server.
I killed all the processes with my id on the machine.
After that I tried to delete a file, I got an error:-
file not removed.Text File busy.
Deletion of directory prompted:-
Directory not empty.
Can anyone help me regarding this...???
Thanks,
Vikas (11 Replies)
Discussion started by: vikasrout
11 Replies
8. Ubuntu
Hello friends. I am currently using Ubuntu 9.10. Its having a lot of features. I have a problem in this operating system that is unable to open Gtalk. Could i get the information to use Gtalk in Ubuntu 9.10. Please reply me. (1 Reply)
Discussion started by: andrepitt77
1 Replies
9. UNIX for Dummies Questions & Answers
We have the Mercurial client installed on our linux machine.
$ hg --version
Mercurial Distributed SCM (version 2.2.3)When I try to invoke it using a cronjob, it fails with the message "command not found".
$ crontab -l
# DO NOT EDIT THIS FILE - edit the master and reinstall.
#... (2 Replies)
Discussion started by: balajesuri
2 Replies
CRON(8) System Manager's Manual CRON(8)
NAME
cron - daemon to execute scheduled commands (ISC Cron V4.1)
SYNOPSIS
cron [-l load_avg] [-n]
DESCRIPTION
Cron should be started from /etc/rc or /etc/rc.local. It will return immediately, so you don't need to start it with '&'. The -n option
changes this default behavior causing it to run in the foreground. This can be useful when starting it out of init.
Cron searches /var/spool/cron for crontab files which are named after accounts in /etc/passwd; crontabs found are loaded into memory. Cron
also searches for /etc/crontab and the files in the /etc/cron.d directory, which are in a different format (see crontab(5)). Cron then
wakes up every minute, examining all stored crontabs, checking each command to see if it should be run in the current minute. When execut-
ing commands, any output is mailed to the owner of the crontab (or to the user named in the MAILTO environment variable in the crontab, if
such exists).
Additionally, cron checks each minute to see if its spool directory's modtime (or the modtime on /etc/crontab) has changed, and if it has,
cron will then examine the modtime on all crontabs and reload those which have changed. Thus cron need not be restarted whenever a crontab
file is modified. Note that the Crontab(1) command updates the modtime of the spool directory whenever it changes a crontab.
Daylight Saving Time and other time changes
Local time changes of less than three hours, such as those caused by the start or end of Daylight Saving Time, are handled specially. This
only applies to jobs that run at a specific time and jobs that are run with a granularity greater than one hour. Jobs that run more fre-
quently are scheduled normally.
If time has moved forward, those jobs that would have run in the interval that has been skipped will be run immediately. Conversely, if
time has moved backward, care is taken to avoid running jobs twice.
Time changes of more than 3 hours are considered to be corrections to the clock or timezone, and the new time is used immediately.
PAM Access Control
On SUSE LINUX systems, crond now supports access control with PAM - see pam(8). A PAM configuration file for crond is installed in
/etc/pam.d/crond . crond loads the PAM environment from the pam_env module, but these can be overriden by settings in the crontab file.
SIGNALS
On receipt of a SIGHUP, the cron daemon will close and reopen its log file. This is useful in scripts which rotate and age log files.
Naturally this is not relevant if cron was built to use syslog(3).
CAVEATS
In this version of cron, /etc/crontab must not be writable by any user other than root. No crontab files may be links, or linked to by any
other file. No crontab files may be executable, or be writable by any user other than their owner.
SEE ALSO
crontab(1), crontab(5), pam(8)
AUTHOR
Paul Vixie <vixie@isc.org>
4th Berkeley Distribution 10 January 1996" CRON(8)