- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Re: crontab problem
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-09-2010 02:16 AM
тАО10-09-2010 02:16 AM
crontab problem
when I wanted to edit crontab file using the following command:-
#crontab -e
The crontab edit file was not opened.
please could anyone help me to fix my problem?
bye.
- Tags:
- crontab
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-09-2010 02:37 AM
тАО10-09-2010 02:37 AM
Re: crontab problem
Crontabs are normally stored in this directory:
/var/spool/cron/crontabs
Assuming that you're trying to look at root's crontab, there should be a file there called root...
Hope this helps,
Regards,
Rob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-09-2010 02:53 AM
тАО10-09-2010 02:53 AM
Re: crontab problem
echo $EDITOR
> The crontab edit file was not opened.
What, exactly, does this mean? What _did_
happen? Did you get some error message?
> please could anyone help me to fix my
> problem?
It might be easier if you supplied some
basic, useful information. Did you try
reading this?:
man crontab
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-09-2010 04:47 AM
тАО10-09-2010 04:47 AM
Re: crontab problem
I looked for the following directory:-
/var/spool/cron/crontabs
I found all these files inside:-
.mrg..root .new..sys .proto..sys sys.new..adm .proto..adm adm uucp.new..cronuucp .proto..cronuucp cronuucp.new..root .proto..root root
the file you mentioned is among these file or not.
If it is among these file so what is the problem
bye.
Hi Steven,
the output of sizer -v command as following:-
# sizer -v
Compaq Tru64 UNIX V5.1 (Rev. 732); Mon Sep 20 10:17:40 EET 2010
echo $EDITOR
the output of echo $EDITOR is nothing appeared.
>What, exactly, does this mean? What _did_
>happen? Did you get some error message?
what exactly happened is when I used this command (crontab -e) to edit crontab file,the editor file did not appeared.
that what happened to me.
bye.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-09-2010 10:01 AM
тАО10-09-2010 10:01 AM
Re: crontab problem
You need to export EDITOR with the path to an editor that "crontab -e" can use.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-09-2010 01:38 PM
тАО10-09-2010 01:38 PM
Re: crontab problem
> an editor that "crontab -e" can use.
Perhaps not. According to the "man" page:
http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/V51_HTML/MAN/MAN1/0073____.HTM
[...] The -e option invokes the editor
specified by the EDITOR environment variable,
or uses /usr/bin/vi by default. [...]
> [...] the editor file did not appeared.
So, the command appeared to do exactly
nothing?
> I found all these files inside:- [...]
ls -l /var/spool/cron/crontabs/root
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-10-2010 11:23 PM
тАО10-10-2010 11:23 PM
Re: crontab problem
<<<
- what error did you get?
there may be a lock file from a previous session?
- if you try "crontab -l"
is there any cron entry listed?
- do you by chance run in a Cluster environment?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-10-2010 11:43 PM
тАО10-10-2010 11:43 PM
Re: crontab problem
> If it is among these file so what is the problem
Yes there's a file called root there, but again I am assuming that you're trying to edit root's crontab...
Can you cat the file ?
# cat root
Does that display what you're expecting to see ?
Is it possible someone accidentally deleted the crontab that you're trying to edit ?
It's quite easy to type crontab -r rather than crontab -e. (remove not edit).
Cheers,
Rob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-13-2010 02:29 AM
тАО10-13-2010 02:29 AM
Re: crontab problem
>>Can you cat the file ?
# cat root
It display what I am expecting to see.
All its contents are there so what that means
and if corntab -e is deleted so how can I return it to its previous state.
bye
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-13-2010 02:40 AM
тАО10-13-2010 02:40 AM
Re: crontab problem
The problem is therefore likely to be with your editor settings as previously suggested.
Try this:
# EDITOR=vi
# export EDITOR
# crontab -e
Cheers,
Rob