06-20-2005
hi zazzybob
i believe my question was not as root login
then do u mean to say there is
no way to view user2's crontab entry loggin as user1
10 More Discussions You Might Find Interesting
1. Linux
How can dump the user account detail? like how long need to change password, password naming policy, how many times will lock account if login failed..
thk a lot (1 Reply)
Discussion started by: zp523444
1 Replies
2. UNIX for Dummies Questions & Answers
Hi!
I'm a bit noob on Unix/Linux world, so sorry any lame question i may make...
Oh.. and my english too.. is not so famous lol..
The deal is to use crontab to change my admin password every weak to something like "mypasswordcurrrentday" that is... i want evey weak to change my password but... (2 Replies)
Discussion started by: OdinPT
2 Replies
3. UNIX for Dummies Questions & Answers
Hi All,
I am user of partcular user of alinux machine. I want have some cronjobs to be done by machine. But i don't have crontab file for me. However i do have crontab installed as /usr/bin/crontab.
Could anyone please suggest how to creat a new cron file for a user? Any help will be highly... (3 Replies)
Discussion started by: bisla.yogender
3 Replies
4. AIX
Good morning everybody. I have just receiedv a complaint from our DBA saying that if he create a scripts to run some Oracle performance scripts using crontab and the scheduling part is ok but the job is failed when I checked on /var/adm/cron/log.
I have tried his scripts using Oracle id directly... (4 Replies)
Discussion started by: kwliew999
4 Replies
5. UNIX for Dummies Questions & Answers
Hi Guys,
Our user crontab files are located at /var/spool/cron/crontabs.
I have to make some modifications to it.
I have all the crontab entries in a file called 'crontab.actual'. I made changes to this file and now I want to reload these changes from the crontab.actual file to my crontab... (12 Replies)
Discussion started by: vandi
12 Replies
6. Solaris
hi,
how can i assign a crontab to my username "user1", here is my current list details;
$ who
root console Nov 15 14:38
user1 pts/1 Dec 14 21:07 (192.168.1.75)
$ pwd
/etc/cron.d
$ ls -alh
total 20
drwxr-xr-x 2 root sys 512 Nov 15 14:37 .... (3 Replies)
Discussion started by: fspalero
3 Replies
7. Shell Programming and Scripting
Hi All,
I am trying to execute a python script from a user's crontab.
/home/user1/UDE/scripts/UdeManager.py
I am at /home/user1.
If I run the command "/home/user1UDE/scripts/UdeManager.py" from the users home directory its working fine.
But when I try to run from user's cron tab its... (3 Replies)
Discussion started by: Tuxidow
3 Replies
8. UNIX for Dummies Questions & Answers
Hi All,
Ref: "build crontab from a text file" in same forum. (I am not allowed to post URL's in the first post)
We are reorganizing our UNIX Crontab file by first making changes in a word pad text file. The intent is to then copy it back to Crontab. Will this work? Copy and Paste does not... (6 Replies)
Discussion started by: nivedhitha
6 Replies
9. HP-UX
Hello Anyone:
I have run into an issue that I have never seen or heard of.
Recently on a specific server I have encountered a random issue that I've not been able to repliate on demand... When I view the processes status of a certain process, the information returned to the screen has a... (2 Replies)
Discussion started by: DEN1022
2 Replies
10. Solaris
Hi everyone,
I got error which is "!bad user (root)" in crontab...
I tried changing password,
I checked etc/cron/cron.allow and cron.deny,
And also I checked the permissions of my files,
its(my crontab script) still not working....
Please help... (12 Replies)
Discussion started by: ijustneeda
12 Replies
talk(1) General Commands Manual talk(1)
Name
talk, otalk - talk to another user
Syntax
talk person [ttyname]
otalk person [ttyname]
Description
The command is a visual communication program which copies lines from your terminal to that of another user.
If you wish to talk to someone on your own machine, then person is just the person's login name. If you wish to talk to a user on another
host, then person is of the form :
host!user
or
host.user
or
host:user
or
user@host
The form user@host is perhaps preferred.
If you want to talk to a user who is logged in more than once, the ttyname argument may be used to indicate the appropriate terminal name.
When first called, it sends the message
Message from TalkDaemon@his_machine...
talk: connection requested by your_name@your_machine.
talk: respond with: talk your_name@your_machine
to the user you wish to talk to. At this point, the recipient of the message should reply by typing
talk your_name@your_machine
It doesn't matter from which machine the recipient replies, as long as his login-name is the same. Once communication is established, the
two parties may type simultaneously, with their output appearing in separate windows. Typing Ctrl-L will cause the screen to be reprinted,
while your erase, kill, and word kill characters will work in talk as normal. To exit, just type your interrupt character; then moves the
cursor to the bottom of the screen and restores the terminal.
Permission to talk may be denied or granted by use of the mesg command. At the outset talking is allowed. Certain commands, in particular
and disallow messages in order to prevent messy output.
In order to use the program with machines on your network that may be running earlier versions of ULTRIX, you must initiate a session with
the command (/usr/ucb/otalk) instead of the command You must also respond to a request from a machine running an older version of the pro-
gram with the command. See the Restrictions section.
Examples
The following example demonstrates how to use the command. In this case, user1, whose system (system1) is running ULTRIX V2.2 initiates a
session with user2, whose system (system2) is running ULTRIX V3.0. User1 types the following:
system1> talk user2@system2
The following message appears on the screen of user2:
Message from Talk_Daemon@system2 at 12:37 ...
talk: connection requested by user1@system1.
talk: respond with: otalk user1@system1
To establish the connection user2 follows the instructions from the Talk_Daemon and types the following at the system prompt:
system2> otalk user1@system1
Restrictions
The version of released with ULTRIX V3.0 uses a protocol that is incompatible with the protocol used in earlier versions. Starting with
ULTRIX V3.0, the program communicates with other machines running ULTRIX, V3.0 (and later), and machines running 4.3 BSD or versions of
UNIX based on 4.3 BSD.
The command is not 8-bit clean. Typing in DEC Multinational Characters (DECMCS) causes the characters to echo as a sequence of a carets (^)
followed by the character represented with its high bit cleared. This limitation makes unusable if you want to communicate using a language
which has DECMCS characters in its alphabet.
Files
to find the recipient's machine
to find the recipient's tty
See Also
mail(1), mesg(1), who(1), write(1), talkd(8c)
talk(1)