Please post the output of the following two commands:
I suspect the filemodes of the directories have the sticky bits set and one of the users is the owner, the other only in the same group. The filemodes will prove this suspicion.
Please also say which filemode you want to have set on newly created files so that we can suggest the correct filemode to set.
My Admin has written a shell script (Filepermission.ksh) with the following commands and provided me 'exeutive' privileges. However, when I try to run the script, I am getting the following error message. Can some one tell me what could be missing? Thank you for your continued support.
Script:
... (0 Replies)
folks;
How can i give a group a sudo permission to execute only some command "like start/stop Apache", so every user in that group can sudo to use this as himself, i mean when he tries to sudo, he will be asked for a password (and make it so he must use his own NT password not a generic one) then... (6 Replies)
Hello All,
I receive a file from another server with file permission rw-r--r-- and owner of the file is the sFTP login id and group is also different from my login id.
Due to this I cannot move the file from and also cannot do anything on it.
Can anyone help on how to change the file... (2 Replies)
We have a script which will move the files from the each user home directory to other location to process the file in the server.
The users put files in their home directory using FTP and the user home dir have 775 permission so the the application user can move the files from the home path to... (11 Replies)
hello
I m trying to enter in a folder through my script but getting permission denied error ..
Is there any command or somthing else so that i can access these folder through my script. (3 Replies)
-rw-r--r-- 1 root wheel 1676 Jul 8 13:40 group
-rw-r--r-- 1 root wheel 3669 Feb 25 2010 passwd
-r--r----- 1 root wheel 1242 Jan 26 2010 sudoers
I can read group and passwd, but i cant read sudoers.. why?
I am curenttly a staff member. (1 Reply)
Good day guys,
I am very new in UNIX and am trying to install an application which uses an application ID that requires administrative privileges (Full control). In most cases, we use SUDO to grant access to this ID however the customer insisted NOT to use SUDO and Root ID is not to be used to... (1 Reply)
I have a file, the long listing output by 'ls -l' is
-rw-r--r-- 1 usera agroup 1246 Jul 7 14:44 temp.R
The file is under a Solaris ZFS file system. As a different user (userb), I did
cp temp.R /tmp
ls -l /tmp/temp.R
-rw-r--r-- 1 userb agroup 1246 Nov 16 14:45 /tmp/temp.R
... (14 Replies)
Hi all,
I am running CentOS6.3 and NFS is giving me a real hard time here:
on my server a folder called /networkh has created with 777 permissions. I have setup NFS server on this server and it is supposed to serve a network.
On my client machine I configed my auto.master:
/nethome... (1 Reply)
This is unfortunately for a Tru64 5.1 PK4 system.
I have Autofs running and it seems to read and mount the NIS maps, however, on a couple of maps, eventhough is says (rw), the user home directory of /home is (ro). See cut and paste Below. This prevents the automounting of Users home... (4 Replies)
Discussion started by: mrmurdock
4 Replies
LEARN ABOUT ULTRIX
talk
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 Alsomail(1), mesg(1), who(1), write(1), talkd(8c)talk(1)