11-09-2007
User dir access using ~ in sh
I am writing code to copy file if user dir exists.
Code snippet :
#!/bin/sh
if [ -d ~user1 ]
then
cp ~user1/file file
else
cp ~user2/file file
fi
This code works if shell is ksh but not if shell is sh.
Can anyone suggest how this can work in sh script?
Thanks,
Ashish
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
How do I give specific user the ablity to create, delete, rename, and alter in a specific directory. I am using redhad 7.2 and would like to give a specific user the rights to a dirc in the main www directory. (1 Reply)
Discussion started by: macdonto
1 Replies
2. UNIX for Dummies Questions & Answers
Hi Guys,
Im trying to set up FTP to my Apache Tomcat dir on my server so my web designer can FTP in and look at things in a live environment.
However at first I couldn't write to the dir, so i change some permissions, and now I cant access it at all!
Here is my LS -all output:
... (4 Replies)
Discussion started by: boarderstu
4 Replies
3. UNIX for Advanced & Expert Users
Hello
i want to ask
how can i let a newly created user to access only one directory and not any other directory at all.: (1 Reply)
Discussion started by: learn82
1 Replies
4. UNIX for Dummies Questions & Answers
Hi!
i'm using FreeBSD 6.2 and hosting my pc to frens
in particular of sensitive information being saved to the PC, i would like to know is it possible for me to restrict user access to their /home dir. only?
and also, i wanted to restrict them listing files under /etc
thanks all! (10 Replies)
Discussion started by: rdns
10 Replies
5. UNIX for Dummies Questions & Answers
Hi all,
if I have a dir with a mixture of files and directories in it and one of the directories *only* has read permission for the owner and I am not the owner - will I see it with an 'ls -la'.
I do not have access to a unix box at present to try this out.
Any thoughts gratefully received (1 Reply)
Discussion started by: ajcannon
1 Replies
6. Linux
Hi Friends,
I have installed a FTP Server on my Linux machine (Fedora 11).
I want the ftp users to be restricted to their own home dir using sftp.
But the said condition is met when the user logs in using ftp over port 21 and when the user logs in using sftp i.e. protocol 22, he/she has... (4 Replies)
Discussion started by: pashy
4 Replies
7. UNIX for Dummies Questions & Answers
I have to move files (one by one) from one dir to another, in such a way that the oldest file should be moved first followed by the latest file. The source dir (from where I am moving files) may contains a minimum of 20K files at any point of time. I am not able to use "ls -ltr" as it throws error... (6 Replies)
Discussion started by: rajesh8s
6 Replies
8. Shell Programming and Scripting
Hi All,
I got access in UNIX box from our client.
I am able to create folder, files, script etc.. in that folder.
here is the issue:
my login/base folder is = /home/ace
I have created 2 folders within it
Script
ScriptLog
in Script folder i have created 2 .ksh file
... (1 Reply)
Discussion started by: ace_friends22
1 Replies
9. UNIX for Dummies Questions & Answers
Whenever i switch from root to another user, by doing su - user, it takes me to home directory of user. This is very annoying as i want to be in same dir to run different commands as root sometimes and sometimes as normal user.
How to fix this? (1 Reply)
Discussion started by: syncmaster
1 Replies
10. AIX
I have searched this quite a long time but couldn't find the right method for me to use. I need to assign read write permission to the user for specific directories and it's sub directories and files. I do not want to use ACL. I do not want to assign user the same group of that directories too.... (0 Replies)
Discussion started by: blinkingdan
0 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