09-29-2008
Franklin52, you are right.. Forgot the E character...
My bad..
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
What is the best way to modify the crontab file??
Edit the file and then use crontab 'filename' ???
I do not know how to use pico editor - so I cannot modify it this way, Any help is appreciated. (3 Replies)
Discussion started by: frustrated1
3 Replies
2. UNIX for Dummies Questions & Answers
I saw a post on here a while back describing how to edit a crontab file when I'm not able to edit it via crontab -e.
Currently, if I try to do a crontab -e, it just comes back with:
# crontab -e
7987
<and then it just hangs there FOREVER>
If I do a crontab -l, it shows me all of the... (1 Reply)
Discussion started by: FredSmith
1 Replies
3. Shell Programming and Scripting
hi
i need to change crontab settings as
minute,hour,day of month,month year,day of week
certain times. for that i need to go as crontab -e. i want to avoid that as its creating many problems in mysystem.
so here i m planning/trying to write a script that will update the settings in crontab... (8 Replies)
Discussion started by: d_swapneel14
8 Replies
4. UNIX for Dummies Questions & Answers
Hi
I am new to Unix and would like some assistance.
I need to edit the crontab file so that a script is set to run at 3:00 am each day.
When I telnet to the sun server and type crontab -e a black screen appears and I am unable to make any changes.
Could you advice on what is needed to... (11 Replies)
Discussion started by: juliet
11 Replies
5. Solaris
Hi..
At linux
I can edit crontab with command
$crontab -e
BUT I don't know to edit crontab at Solaris
because I tried with command $crontab -e
I can't do that
Can you help me...?
Thanks for solution
regards,
srilinux (25 Replies)
Discussion started by: srilinux
25 Replies
6. Shell Programming and Scripting
Hi All,
There are some cron jobs scheduled already by someone, now I have to make some changes to the schedule timings. Please advise me.
thanks,
Raju (2 Replies)
Discussion started by: rajus19
2 Replies
7. Shell Programming and Scripting
Hi,
Can some one tell me if we can configure the jobs in crontab using a shell script.
I know it can be done easily by using "crontab -e", but i just want to know whether we can add a job into the crontab using a shell script.
If it can be done, plz suggest the procedure to do it.
If it... (6 Replies)
Discussion started by: rudrarajumk
6 Replies
8. UNIX for Dummies Questions & Answers
Hi Guys,
I need to edit the crontab on one of my unix systems. When I execute crontab -e, nothing happens, then I get an error '666' and can't type anything else at the cli.
I tried resizing the window, but still got the same error. I'm using the run user and I've checked the permissions on... (0 Replies)
Discussion started by: bbbngowc
0 Replies
9. UNIX for Dummies Questions & Answers
Hi,
I have a solaris 10 box. And I want to schedule a cronjob.But it gives the following error
bash-3.2$ crontab -l
crontab: can't open your crontab file.
bash-3.2$ EDITOR=vi
bash-3.2$ export EDITOR
bash-3.2$ crontab -e
crontab: can't open your crontab file.
I checked in... (12 Replies)
Discussion started by: Rossdba
12 Replies
10. Shell Programming and Scripting
Hi,
I m setting up my crontab for the very first time. I m a non-root user and this is linux
$ export EDITOR=vi
$ crontab -e
no crontab for user1 - using an empty one
crontab: installing new crontab
"/tmp/crontab.uW0JNx":1: bad command
errors in crontab file, can't install.
Do you want... (3 Replies)
Discussion started by: mohtashims
3 Replies
BADSECT(8) System Manager's Manual BADSECT(8)
NAME
badsect - create files to contain bad sectors
SYNOPSIS
/sbin/badsect sector ...
DESCRIPTION
Badsect makes a file to contain a bad sector. Normally, bad sectors are made inaccessible by the standard formatter, which provides a for-
warding table for bad sectors to the driver; see bad144(8) for details. If a driver supports the bad blocking standard it is much prefer-
able to use that method to isolate bad blocks, since the bad block forwarding makes the pack appear perfect, and such packs can then be
copied with dd(1). The technique used by this program is also less general than bad block forwarding, as badsect can't make amends for bad
blocks in the i-list of file systems or in swap areas.
Adding a sector which is suddenly bad to the bad sector table currently requires the running of the standard DEC formatter, as UNIX does
not supply formatters. Thus to deal with a newly bad block or on disks where the drivers do not support the bad-blocking standard badsect
may be used to good effect.
Badsect is used on a quiet file system in the following way: First mount the file system, and change to its root directory. Make a direc-
tory BAD there and change into it. Run badsect giving as argument all the bad sectors you wish to add. (The sector numbers should be
given as physical disk sectors relative to the beginning of the file system, exactly as the system reports the sector numbers in its con-
sole error messages.) Then change back to the root directory, unmount the file system and run fsck(8) on the file system. The bad sectors
should show up in two files or in the bad sector files and the free list. Have fsck remove files containing the offending bad sectors, but
do not have it remove the BAD/nnnnn files. This will leave the bad sectors in only the BAD files.
Badsect works by giving the specified sector numbers in a mknod(2) system call (after taking into account the filesystem's block size),
creating a regular file whose first block address is the block containing bad sector and whose name is the bad sector number. The file has
0 length, but the check programs will still consider it to contain the block containing the sector. This has the pleasant effect that the
sector is completely inaccessible to the containing file system since it is not available by accessing the file.
SEE ALSO
mknod(2), bad144(8), fsck(8)
BUGS
If both sectors which comprise a (1024 byte) disk block are bad, you should specify only one of them to badsect, as the blocks in the bad
sector files actually cover both (bad) disk sectors.
On the PDP-11, only sector number less than 131072 may be specified on 1024-byte block filesystems, 65536 on 512-byte block filesystems.
This is because only a short int is passed to the system from mknod.
3rd Berkeley Distribution BADSECT(8)