01-09-2013
Folder permission
Hi,
I created user1 & user2 on my Linux machine. User2 cannot access home directory of user1. How user2 access the user1 home directory without changing owner of the directory. from root user, i tried chmod 755 /home/user1. But user2 trying to change directory it provides permission denied error.
Thanks for advance
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
I tried to create a new folder inside a folder A but was given an error "Permission denied". Any idea? (4 Replies)
Discussion started by: trivektor
4 Replies
2. Shell Programming and Scripting
Hello ,
I am trying to write a unix shell script to compare folder permission to say drwxr-x-wx and then send an email to my id in case the folders don't have the drwxr-x-wx permissions set for them .
I have been trying to come up with a script for few days now , pls help me:( (2 Replies)
Discussion started by: nairshar
2 Replies
3. HP-UX
Hi guys,
When I switch my user. I cant go to one of the folders. seems that this user has no right to access the folder. can you please help me to give the right to this user in order for him to access to the folder? it gives me permission denied. (2 Replies)
Discussion started by: messi777
2 Replies
4. UNIX for Dummies Questions & Answers
Hi All,
I want to change a permission 755 only for a folder <log> under the directory recursively /home . but all other folder permission remain same under /home
Thanks in advance
Chakkaravarthy (8 Replies)
Discussion started by: chakkaravarthy
8 Replies
5. HP-UX
Hi
I am a normal user on a HP-UX system which is meant for a large group.
There are few directories which I think i am owner of. (Name of these directories is same as my username, and I usually have all the permissions in these directories).
I was trying to give read and execute... (2 Replies)
Discussion started by: grvs
2 Replies
6. UNIX for Advanced & Expert Users
Hi Guys,
Is there a command or some way whenever any file is created in a folder is having a default permission.
Cheers!!! (2 Replies)
Discussion started by: mac4rfree
2 Replies
7. Shell Programming and Scripting
hello friends,
By mistake I have run find / -type f -exec chmod 644 {} \;
now all permission has been chaged of /bin
I am not able to change the permission. I am working on the virtuozzo VPS.
Is their any way to retrieve the permission to 770 to /bin
Note /bin/chmod also not executing... (2 Replies)
Discussion started by: sharlin
2 Replies
8. Solaris
I need to transfer directories/files between 2 Unix servers, with same folder permission.
I tried scp, but it retains the the permissions, but changes the owner of the directory/file to the user used to copy them to the destination. I don't want that to happen.
If possible without any other... (6 Replies)
Discussion started by: Pandee
6 Replies
9. Red Hat
Hi All,
What is the use of execute permission for a folder.
I know "for execute a file(script file) we have to provide execute permission to that respective file".But what is the use to give execute permission to folder.Is it equal to read permission ?
Regards,
Mastan (1 Reply)
Discussion started by: mastansaheb
1 Replies
10. UNIX for Dummies Questions & Answers
Hi,
Call me stupid but i accidentally executed following command :
find $INSTALLDIR/ -type f -exec chmod 644 {} \;
now after which I am not able to run any command in system even ls command is giving me error for "permission denied" :( (5 Replies)
Discussion started by: itajooba
5 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)