Sorry to I am not familiar with script writing ,
attach is the /etc/profile in my system , we have limit each user can only have one login in the system . When the user login , if the system found the user have a dead process in the system , the system will confirm the user to kill the previous... (1 Reply)
Hello there,
I would like to know how can i prevent a normal user (not root user) from accessing his .profile and editing its information?
Also, how can i prevent this user from deleting a certain file named "script"?
Any help in that?
Thanks in advance, (3 Replies)
Hello Intelligent Life Forms (I hope)
This should be a snap for some of you.
I need to copy the /usr .profiles from 1 sco system to another.
Migrating to a new server.
I've tried a recursive copy to the target system with a NFS mount point from the source. Wouldn't do it permissions... (2 Replies)
Scenario: a non-root user is under primary group "devel" and I change their primary group to "nondevel"; I then want to be able to give the user a command which refreshes their user profile so that any new files created under their session are assigned to the new group.
What is the command for... (1 Reply)
Hello
I really wonder what's trap in etc/profile and in each user .profile.
I try to google for it but I think I have no luck. Mostly hit is SNMP traps which I think it is not the same thing.
I want to know ...
1. What's a "trap 2 3" means and are there any other value I can set... (4 Replies)
Hello ,
i am on sles 11, and i can't figure out how can i locate my profile file,
the one that is use for setting the environment when i log in.
oracle@r200:~> cd
oracle@r200:~> pwd
/opt/oracle
oracle@r200:~> echo $SHELL
/bin/bash
oracle@r200:~>
oracle@r200:~> cat .profile
cat: .profile:... (4 Replies)
Discussion started by: tonijel
4 Replies
LEARN ABOUT DEBIAN
calife.auth
CALIFE.AUTH(5) BSD File Formats Manual CALIFE.AUTH(5)NAME
calife.auth -- format of the calife authorization file
DESCRIPTION
The calife.auth files are files consisting of newline separated records, one per user, containing three colon (``:'') separated fields.
These fields are as follows:
name User's login name / @group.
shell User's shell
user1,user2,...,usern
List of logins allowed for the user name
The name field is the login used to access the computer account.
The login name must never begin with a hyphen (``-''); also, it is strongly suggested that neither upper-case characters or dots (``.'') be
part of the name, as this tends to confuse mailers. No field may contain a colon (``:'') as this has been used historically to separate the
fields in the user database.
One alternative syntax is to use @group to specify that any user in the given group is allowed to use calife to become root.
The shell field is the command interpreter the user prefers. If there is nothing in the shell field, the user's current shell as found in
the (/etc/passwd) file is assumed.
If the shell field is '*', then the account is considered as locked and access is denied.
If the third parameter is specified, it is assumed to be the list of login the current user has the right to become. It enables use of calife
for non-root only accounts.
calife.auth is placed in /etc.
EXAMPLE
# calife.auth-dist
#
# Format
#
# name[:shell_to_be_run][:user1,user2,usern]
#
fcb
roberto:/bin/tcsh
pb::guest,blaireau
SEE ALSO calife(1), su(1)HISTORY
A calife.auth file format appeared in DG/UX and SunOS, written for Antenne 2 in 1991. It has evolved with the extra shell specification. The
login list was reintroduced in 2.7.
AUTHOR
Ollivier Robert <roberto@keltia.frmug.fr.net>
BSD September 25, 1994 BSD