07-03-2003
working now
It is working now . I noticed 2 variables were not set . I set the same and tested. It's working now.
BTW , thanks a lot for ur help.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi everyone, I'n new on this... And I don't have experience.
I need to know how to enable rsh between solaris and tru64.
I don't know what i need to modify or install. I really don't have idea.
If somebody has documentation about this, or has a procedure to do this.
I really will... (1 Reply)
Discussion started by: cm247a
1 Replies
2. Solaris
Hi Guys,
Please suggest how to stop rsh on Solaris 10
Thanks
Manu (1 Reply)
Discussion started by: b_manu78
1 Replies
3. 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
4. Solaris
Hi Friends,
I am trying to execute rsh commands from Solaris 10 system to AIX system.
When I give;
Solaris10# rsh <hostname> ls -l , it gives me an error
rshd : 0826-826 The host name for your address is not known
At the same time,
Solaris10# rsh <hostname> ---- gives me remote shell of... (25 Replies)
Discussion started by: jumadhiya
25 Replies
5. UNIX for Dummies Questions & Answers
All,
I have two AIX 5.3 systems that needs to run rsh commands on a Solaris 8 system, and one is failing. One, xx402 is a dedicated machine, and the other, xx452 is a virtual one on (via VIO).
The xx402 has no problem with the rsh commands but I keep getting "Permission Denied" when the... (5 Replies)
Discussion started by: kjbaumann
5 Replies
6. Solaris
dear all
Please suggest how to stop rsh on Solaris 10
Thanks
murad jaber (2 Replies)
Discussion started by: murad.jaber
2 Replies
7. Solaris
hi
I want to run a script every 30 minutes in Solaris 10 x86
I tried
0,30 * * * * /tmp/script.sh
but it does not run.
any idea? (1 Reply)
Discussion started by: melanie_pfefer
1 Replies
8. Solaris
Unable to execute commands using rsh in Solaris 9 and 10.
When I execute this command " rsh -n 172.16.67.91 ls -l " I am getting this error message.
::ffff:172.16.67.91: Connection refused
Please guide me how to enable rsh.
Thanks & Regards
Durgaprasad (1 Reply)
Discussion started by: durgaprasadr13
1 Replies
9. UNIX for Dummies Questions & Answers
Can anyone point me in the right direction..
I have a test system which requires vxWorks to be loaded via TCPIP
I am using a Sun ultra10 box with Sol 9.0 installed as the server
I have configured the server and am able to load the boot image without any problems. I assume it is using the... (0 Replies)
Discussion started by: shortsrkt
0 Replies
10. Solaris
Hi
we run rsh (password-less) among solaris 9/10 boxes very frequently and would like to know if there exist any logs which will capture either login session or the commands run (using rsh) or with any other info.
TIA
Reddy (0 Replies)
Discussion started by: reddyr
0 Replies
LEARN ABOUT MOJAVE
crontab
CRONTAB(1) BSD General Commands Manual CRONTAB(1)
NAME
crontab -- maintain crontab files for individual users (V3)
SYNOPSIS
crontab [-u user] file
crontab [-u user] { -l | -r | -e }
DESCRIPTION
The crontab utility is the program used to install, deinstall or list the tables used to drive the cron(8) daemon in Vixie Cron. Each user
can have their own crontab, and they are not intended to be edited directly.
(Darwin note: Although cron(8) and crontab(5) are officially supported under Darwin, their functionality has been absorbed into launchd(8),
which provides a more flexible way of automatically executing commands. See launchctl(1) for more information.)
If the /usr/lib/cron/cron.allow file exists, then you must be listed therein in order to be allowed to use this command. If the
/usr/lib/cron/cron.allow file does not exist but the /usr/lib/cron/cron.deny file does exist, then you must not be listed in the
/usr/lib/cron/cron.deny file in order to use this command. If neither of these files exists, then depending on site-dependent configuration
parameters, only the super user will be allowed to use this command, or all users will be able to use this command. The format of these
files is one username per line, with no leading or trailing whitespace. Lines of other formats will be ignored, and so can be used for com-
ments.
The first form of this command is used to install a new crontab from some named file or standard input if the pseudo-filename '-' is given.
The following options are available:
-u Specify the name of the user whose crontab is to be tweaked. If this option is not given, crontab examines ``your'' crontab, i.e.,
the crontab of the person executing the command. Note that su(1) can confuse crontab and that if you are running inside of su(1) you
should always use the -u option for safety's sake.
-l Display the current crontab on standard output.
-r Remove the current crontab.
-e Edit the current crontab using the editor specified by the VISUAL or EDITOR environment variables. The specified editor must edit
the file in place; any editor that unlinks the file and recreates it cannot be used. After you exit from the editor, the modified
crontab will be installed automatically.
FILES
/usr/lib/cron/cron.allow
/usr/lib/cron/cron.deny
DIAGNOSTICS
A fairly informative usage message appears if you run it with a bad command line.
SEE ALSO
crontab(5), compat(5), cron(8), launchctl(1)
STANDARDS
The crontab command conforms to IEEE Std 1003.2 (``POSIX.2''). The new command syntax differs from previous versions of Vixie Cron, as well
as from the classic SVR3 syntax.
AUTHORS
Paul Vixie <paul@vix.com>
BSD
December 29, 1993 BSD