Sponsored Content
Top Forums UNIX for Advanced & Expert Users Cannot access: No such file or directory Post 302438035 by 78air on Saturday 17th of July 2010 03:03:56 PM
Old 07-17-2010
I'm on holiday for the next couple of weeks so the files MUST wait. Thanks methyl for your answer. I'll try to post the output as soon as possible and let you know. You'll hear from me soon.
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

failed to access directory thru ftp

Hi all, I am a beginner to unix and ftp too.So i request your valuable comments. Requirement: I want to put a specific file into a server(linux) and under a particular directory path in that server as /caps/details/data/ Problem : I login to that server through the command `ftp... (1 Reply)
Discussion started by: DILEEP410
1 Replies

2. UNIX for Dummies Questions & Answers

How to access an directory with spaces

I am getting an error while trying to access a directory created with spaces in between, i couldn't able to login into that directory could you please suggest me what should i do to access that directory or if i want to rename that directory what should i do. Directory Name: MH PLR 2005... (1 Reply)
Discussion started by: Ariean
1 Replies

3. Solaris

Restricting FTP access for a particular directory

Dear All, I have created a user called "x" who is allowed only to FTP and it is working fine. Here my problem is, I want to give access to a particular directory say for eg:- /dump/test directory. I don't find any option in the useradd command to restrict access to this particular directory only... (1 Reply)
Discussion started by: Vijayakumarpc
1 Replies

4. Solaris

User with limited access to one directory

is there a way to create a user and limit him to read,write and execute only in one direcotry. the directory is already exsist and it belongs to dba group. i would like to make this user can't even cd to another directory or even if he can he cant do anything in the other directories. if... (7 Replies)
Discussion started by: q8devilish
7 Replies

5. UNIX for Advanced & Expert Users

Solaris auditing (file access logging) for specific directory only.

Hello, We need to log the operations that specific user on Solaris 10 (SPARC) is performing on one directory and it's contents. I was able to configure solaris auditing service (auditd) and it works fine. The only problem is that auditd logs huge amount of unneeded information. We need to log... (0 Replies)
Discussion started by: +Yan
0 Replies

6. UNIX for Advanced & Expert Users

about the access permission of users home directory

RHEL5.0 As we know, when root create a new user, a new home directory will be created : /home/user I want to know what determine the access permission of /home/user . Thanks! (1 Reply)
Discussion started by: cqlouis
1 Replies

7. AIX

openssh chroot facility and directory access

Good day. I currently have a request to have sftp access to a specific directory for a user(s). They can have access to that folder only, and nothing below it. Now here is the gotcha that seems to be catching me. The folder they need access to is NOT owned by root, and most of the parent... (0 Replies)
Discussion started by: smurphy_it
0 Replies

8. Red Hat

cannot access a directory with samba

path = /opt writeable = yes ; browseable = yes # guest ok = no valid users = oracle path = /opt/TEST8000/oracle/apps/apps_st/appl/ffcl/12.0.0/reports/US writeable = yes ; browseable = yes valid users = oracle path... (1 Reply)
Discussion started by: rehantayyab82
1 Replies

9. Ubuntu

No access to etc directory

Hi, I'm new to this... but I am unable to see /etc, however I can access it via gknautilus... but as superuser I'm getting told no such file or directory via terminal (15 Replies)
Discussion started by: GaryW
15 Replies

10. AIX

Samba 3.6 on AIX 7.1 - Windows 10 Access to AIX file shares using Active Directory authentication

I am running AIX 7.1 and currently we have samba 3.6.25 installed on the server. As it stands some AIX folders are shared that can be accessed by certain Windows users. The problem is that since Windows 10 the guest feature no longer works so users have to manually type in their Windows login/pwd... (14 Replies)
Discussion started by: linuxsnake
14 Replies
LS(1)							      General Commands Manual							     LS(1)

NAME
ls, lc - list contents of directory SYNOPSIS
ls [ -dlmnpqrstuFQ ] name ... lc [ -dlmnpqrstuFQ ] name ... DESCRIPTION
For each directory argument, ls lists the contents of the directory; for each file argument, ls repeats its name and any other information requested. When no argument is given, the current directory is listed. By default, the output is sorted alphabetically by name. Lc is the same as ls, but sets the -p option and pipes the output through mc(1). There are a number of options: -d If argument is a directory, list it, not its contents. -l List in long format, giving mode (see below), file system type (e.g., for devices, the # code letter that names it; see intro(3)), the instance or subdevice number, owner, group, size in bytes, and time of last modification for each file. -m List the name of the user who most recently modified the file. -n Don't sort the listing. -p Print only the final path element of each file name. -q List the qid (see stat(3)) of each file; the printed fields are in the order path, version, and type. -r Reverse the order of sort. -s Give size in Kbytes for each entry. -t Sort by time modified (latest first) instead of by name. -u Under -t sort by time of last access; under -l print time of last access. -F Add the character / after all directory names and the character * after all executable files. -L Print the character t before each file if it has the temporary flag set, and - otherwise. -Q By default, printed file names are quoted if they contain characters special to rc(1). The -Q flag disables this behavior. The mode printed under the -l option contains 11 characters, interpreted as follows: the first character is d if the entry is a directory; a if the entry is an append-only file; D if the entry is a Unix device; L if the entry is a symbolic link; P if the entry is a named pipe; S if the entry is a socket; - if the entry is a plain file. The next letter is l if the file is exclusive access (one writer or reader at a time). The last 9 characters are interpreted as three sets of three bits each. The first set refers to owner permissions; the next to permissions to others in the same user-group; and the last to all others. Within each set the three characters indicate permission respectively to read, to write, or to execute the file as a program. For a directory, `execute' permission is interpreted to mean permission to search the directory for a specified file. The permissions are indicated as follows: r if the file is readable; w if the file is writable; x if the file is executable; - if none of the above permissions is granted. SOURCE
/src/cmd/ls.c /bin/lc SEE ALSO
stat(3), mc(1) LS(1)
All times are GMT -4. The time now is 10:40 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy