SHM

[Gyber]

I've just come across SHM in our new HPUX 11i v3 RX2660 server. Having used SAM all the time up to now, setting up CRON jobs through CRONTAB or VI is not easy for a relatively inexperienced HPUX user. SAM had a relatively easy text interface for setting up all our jobs. The question is: Are you going to put his feature back, or is there an easy CRONTAB editor around that could do the same thing?

[Tim Nelson]

1) SAM has been obsoleted in 11.31.

2) Learn the ways of unix by NOT using a dummied down interface.

3) crontab -e (edit your crontab and save it ) man crontab for more details.

[Steven E. Protter]

Shalom,

As Bill Hassell said to me in immortal words 5.5 years ago that inspired me to start ITRC.

Real sysadmins don't suse guis

I'm so not sam dependent I didn't even know sam was obsolete.

I'm sure SHM has the same basic toys, but you need to know how to fly without a gui

SEP

[Torsten.]

SAM is dead and we already miss him ... ;-)

SMH has 2 interfaces, web- and text based.

IMHO not every old SAM feature is already included.

Did you try

crontab -e root

[Gyber]

Thanks for all your replies. See attached URL.
http://docs.hp.com/en/B2355-60130/sam.1M.html

I crashed and burned when confronted with VI (Crontab -e just invokes VI to edit it)

Its time to learn VI I suspect because SHM definately doesn't have a CRON editor in it. I think this was a retrograde move by HP (And the SAM development team), this was a feature that could quite so easiliy gone into the SHM web interface.

[Tim Nelson]

Yep. I would say if you intend on being a UNIX admin and do not know VI then you got a looooonnnnnggggg way to go.

Learn it quick..Plenty of www resources. It will take you only 15 minutes or so. Print yourself out a cheat sheet.


Another goofy option. crontab -l > myfile.txt

Use your favorite ftp software, double-click on myfile.txt. This with open it with your favorite windows editor. make changes. save back to ftp directory.

crontab < myfile.txt

will load the newly changed file.

[Marek Podmaka]

Another option:
# VISUAL=your_editor_cmd
# EDITOR=your_editor_cmd

crontab just invokes your configured editor in environment variables. There are 2 of them and I don't know which one crontab uses.

But anyway, be sure that you are able to use editor, which you will have available on root partition upon emergency recovery (which is usually vi).