Sponsored Content
Operating Systems Solaris unable to open directory from user Post 302346439 by spandhan on Saturday 22nd of August 2009 03:14:54 AM
Old 08-22-2009
hi praveen
how r u
just try to give full permissions for df
in /usr/sbin/df
then try
regards
spandhan

Quote:
Originally Posted by tv.praveenkumar
when ever i trying to give df -k from user showing permisson denied for one directory named samba.if i trying to give from root user samba directory is opening.

shut@praveen#df -k

df: cannot statvfs /samba/tcgt_tendering: Permission denied
if i give from root user (df -k)


root@praveen#
Filesystem kbytes used avail capacity Mounted on


/dev/vx/dsk/app2dg/samba 55737934 51096837 4125003 93% /samba/tcgt_tendering


shut@praveen$ cd /dev/vx/dsk/app2dg/
shut@praveen$ ls -l
total 0
brw------- 1 root root 232,23002 Apr 23 2003 bhelapp
brw------- 1 root root 232,23000 Apr 23 2003 bhelapp2
brw------- 1 root root 232,23003 Apr 23 2003 bhelspool
brw------- 1 root root 232,23004 Jan 5 2007 iplanet
brw------- 1 root root 232,23001 Apr 23 2003 ora9ias2
brw------- 1 root root 232,23005 Jun 26 2003 ora9inew
brw------- 1 root root 232,23009 May 17 2005 samba


remaining all directories having same peermissions like samba,but in point of samba directory showing permission denied...

plz can any body tells this difference..
 

9 More Discussions You Might Find Interesting

1. Post Here to Contact Site Administrators and Moderators

Unable to open thread

I am unable to open the mimesender thread. I get the following message when clicking on https://www.unix.com/showthread.php?p=33233#post33233 : (2 Replies)
Discussion started by: dangral
2 Replies

2. UNIX for Dummies Questions & Answers

xhost: unable to open display????

I am a dba, not an sa, that recently had to take over administering an HP-UX server. Needless to say I am not in a comfortable area, but found out that of all people I am the most knowledgeable on unix here .... scary thought I know. I am having troubles exporting my display to a Windows XP... (5 Replies)
Discussion started by: soestx
5 Replies

3. UNIX for Advanced & Expert Users

Other than root user .Normal user is unable to create files

Hi all, I am using Sun Solaris 9 .In this system normal users unable to create files from the command line.I added these users in bin,adm and even root group i found them unable to create a file. (1 Reply)
Discussion started by: mallesh
1 Replies

4. Solaris

Unable to open remote connections

Hello everybody, This is an unusual problem that I am facing on my Solaris 9 on Sun Blade 150 workstation. I can ping remote machines (outside subnet) but I can't open up a connection/port on those machines. For example, `ping ftp.xyz.com` gives ftp.xyz.com is alive but if I do a `ftp... (1 Reply)
Discussion started by: red_crab
1 Replies

5. UNIX for Advanced & Expert Users

unable to create any directory that uses numbers as the directory name

Version-Release number of selected component (if applicable): ================================================================== root@server # cat /etc/redhat-release Red Hat Enterprise Linux ES release 4 (Nahant Update 5) root@server # uname -a Linux server.integrityserver.net... (16 Replies)
Discussion started by: fed.linuxgossip
16 Replies

6. Red Hat

cannot set user id: Resource temporarily unavailable (not open file/open process related)

First post, sorry to be a bother but this one has been dogging me. I have a process user (java application server) that trips a resource limit every couple weeks and need help finding what limit we're hitting. First, this is what's running: This is the error when jobs are run or the... (0 Replies)
Discussion started by: Katahdin
0 Replies

7. Solaris

Unable to create or delete a directory in /usr with root user

Hi All, I am trying to uninstall jdk 1.5 from my Solaris 10 64 bit but some how was not successful.so tried to delete the folder of jdk from /usr but its throughing error as: Unable to remove directory jdk: Read-only file system Even I tried to create a dir in /usr but its not allowing me... (4 Replies)
Discussion started by: Pshah
4 Replies

8. Solaris

Unable to open Crontab

Hi, I have 2 solaris server. I can able to open to see cron entry by using crontab -l in one of the server. I cant able to open another server. How to check if crontab is fixed in that server. If not then how to make a crontab in that server. Please advice. Thanks, Mani ----------... (1 Reply)
Discussion started by: Mani_apr08
1 Replies

9. Ubuntu

Unable to open Gtalk.

Hello friends. I am currently using Ubuntu 9.10. Its having a lot of features. I have a problem in this operating system that is unable to open Gtalk. Could i get the information to use Gtalk in Ubuntu 9.10. Please reply me. (1 Reply)
Discussion started by: andrepitt77
1 Replies
chroot(2)							System Calls Manual							 chroot(2)

NAME
chroot() - change root directory SYNOPSIS
DESCRIPTION
causes the named directory to become the root directory, the starting point for path searches for path names beginning with path points to a path name naming a directory. The user's working directory is unaffected by the system call. The entry in the root directory is interpreted to mean the root directory itself. Thus, cannot be used to access files outside the subtree rooted at the root directory. Security Restrictions The effective user ID of the process must be a user with the privilege to change the root directory. See privileges(5) for more information about privileged access on systems that support fine-grained privileges. RETURN VALUE
returns the following values: Successful completion. Failure. is set to indicate the error. ERRORS
fails and the root directory remains unchanged if one or more of the following is true: Any component of the path name is not a directory. The named directory does not exist or a component of the path does not exist. The effective user ID is not a user who has the privilege. path points outside the allocated address space of the process. The reliable detection of this error is implementation dependent. The length of the specified path name exceeds bytes, or the length of a component of the path name exceeds bytes while is in effect. Too many symbolic links were encountered in translating the path name. WARNINGS
Obsolescent Interfaces is to be obsoleted at a future date. SEE ALSO
chroot(1M), chdir(2), privileges(5). STANDARDS CONFORMANCE
TO BE OBSOLETED chroot(2)
All times are GMT -4. The time now is 05:16 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy