# ls -la /home/user1
drwxrwxrwx 8 user1 staff 4096 Apr 19 2011 .
drwxr-xr-x 8 bin bin 256 Feb 08 2011 ..
drwx---r-x 2 user1 staff 256 Apr 13 2011 dir1
# su - user2
$ cd /home/user1
$ ls dir1
ls: dir1: The file access permissions do not allow the specified action.
$
So: dir1 access is allowed for others, but slill no go! If we change dir1 owner to root:system(all perms stays), user2 is allowed to list dir1.
This is not happening on Linux.
Sorta new to Unix. great site here.
I have SCO server with (5) 16 port Digi-boards and 5 line printers. For 3 years we've had no problems, till now... All of a sudden I get terminals and printers locking up. Killed the PID's for these particular situations. No help. So I disable the tty post... (10 Replies)
Hey folks, I've been charged with the job of finding out who's been screwing around with the download counts on our site. So now I have this huge list of IP's that I supposed to match to such and such developer.
I was told by one guy that I should just do a traceroute and that'd tell me where... (2 Replies)
Hello Everyone,
I am currently running a large Server with Veritas Volumen Manager, attached to a EMC.
uname -a
SunOS 5.8 Generic_117350-47 sun4u sparc SUNW,Sun-Fire-880
I have one directory that tends to change to a file.Once in a while and always in different time.The file is the... (1 Reply)
A perplexing mystery...
please note that i am not a lacky, and the error below is misleading
recently something i do all the time broke (a script).
now when i run this script i get this error.
/usr/bin/awk: 0403-027 The parameter list is too long.
note that the (parameter list is... (9 Replies)
I burned identical raw encrypted data to three cds using my new external Toshiba drive. My internal IBM read only drive does not get an I/O Error when reading in Circumstance #1, but does get an I/O Error in Circumstance #2. But, the Toshiba drive can do both circumstances without an error.
... (1 Reply)
Can I make use of two command variable in case statement
case $2 $3 in
stp)
Firewall disabled
echo " Changing the http Proxy configuration "
;;
str)
Firewall enabled
echo " Setting right http Proxy... (4 Replies)
Hi everyone,
I can't seem to understand the behavior of sort on a particular case.
cat tmp25
1 a
10 b
20 c
2 d
I do that:
sort -k1,1 tmp25
1 a
10 b
2 d
20 c
This one I understand, it's what i expected, from a string point of view 1<10<2<20
sort -k1... (9 Replies)
Hi Folks,
I am running on a CentOS 6.3 server, whose primary function until recently has been my Zimbra mail server exclusively. I added wordpress and I have not been disappointed, with this one exception of Apache mod_rewrite. I have already tried to set selinux to permisive to eliminate that... (5 Replies)
so i noticed that when a shell script has a function defined in it, running "sh -x" on that shell script from the command line doesnt show what the function is doing. i like this.
is there anyway for anyone to get around that? to be able to see exactly what a function or functions are doing? (4 Replies)
Discussion started by: SkySmart
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