08-28-2008
When I cd to oink, it says oink does not exist.
When I ls oink, it gives me a permission denied. I would have thought allowing anonymous access would take care of permissions.
10 More Discussions You Might Find Interesting
1. Windows & DOS: Issues & Discussions
Hi,
How can I mount a Windows share (over samba) on an AIX machine?
I know there is a utility called smbmount on Linux, but alas, I cannot find out how to the same thing on AIX.
anyone have any ideas?
thanks! (3 Replies)
Discussion started by: szahir1
3 Replies
2. Linux
hello everybody
i have one quetion :( about how i can share my file in windows to use it in linux
explane
i have to opreating system
windows xp and linux fedore core and unix ( sun solaris 10 )
and i want to open me file that is storege in windows <<< want to open it in unix or... (4 Replies)
Discussion started by: msn22
4 Replies
3. HP-UX
is it possible? i will only config on the windows side. is there a third party software to help me accomplish this? tnx (3 Replies)
Discussion started by: Amaru
3 Replies
4. UNIX for Advanced & Expert Users
We are trying to mount a Unix share drive on a Windows 2003 server to avoid transfering files accross the network using sftp. I can see shared drives on the Solaris server using the "share" command. How can I mount the drives on my Windows server so that I can read them directly. Do I need... (2 Replies)
Discussion started by: rbdenham
2 Replies
5. Solaris
please help me,,i need step to mount windows share folder,,i try samba and nfs and it didnt work (in my linux server the command is fine),,can somenone give me an example for this to be done? (0 Replies)
Discussion started by: Cellscript
0 Replies
6. UNIX for Dummies Questions & Answers
Hi whan i am trying to mount a windows share on linux i received the following error can some one help me with thsi
# mount -t cifs \\\\servername\testdata -o username=xw27,password=*es*feed /test
Mounting the DFS root for a particular server not implemented yet
No ip address specified... (5 Replies)
Discussion started by: robo
5 Replies
7. UNIX for Dummies Questions & Answers
I know how to mount my share via /etc/fstab automatically when the system boots but since I do not have root permission to access the /etc/fstab nor do I think that the system admin wants me to add an entry in /etc/fstab all together. So what file could I add my mount entry in?
mount -t cifs... (8 Replies)
Discussion started by: metallica1973
8 Replies
8. UNIX for Advanced & Expert Users
Unix Expects,
I am trying to connect to Unix server to windows share point using ftp or fstp. I want to get excel file from windows share to unix server.
But i am not able to do it. Can you please help me on this. :confused:
Cheers (6 Replies)
Discussion started by: AraR87
6 Replies
9. UNIX for Beginners Questions & Answers
Hi Folks -
I need to mount a Windows Share to a Linux server. What is the best/easiest way to do this?
Is this 'how-to' guide accurate:
How to Share Files Between Windows and Linux
Or is there a better method you could share?
Thanks! (8 Replies)
Discussion started by: SIMMS7400
8 Replies
10. UNIX for Advanced & Expert Users
Hi,
I need to mount a directory from a Windows server to a CentOS box.
The Windows server used is Windows Server 2003, and the path to the directory that I want to mount on CentOS is C:\Tomcat6\webapps\NASApp\logs.
I am not sure of the correct way to mount this on CentOS, as most of the... (2 Replies)
Discussion started by: anaigini45
2 Replies
LEARN ABOUT NETBSD
access
ACCESS(2) BSD System Calls Manual ACCESS(2)
NAME
access -- check access permissions of a file or pathname
LIBRARY
Standard C Library (libc, -lc)
SYNOPSIS
#include <unistd.h>
int
access(const char *path, int mode);
DESCRIPTION
The access() function checks the accessibility of the file named by path for the access permissions indicated by mode. The value of mode is
the bitwise inclusive OR of the access permissions to be checked (R_OK for read permission, W_OK for write permission and X_OK for exe-
cute/search permission) or the existence test, F_OK. All components of the pathname path are checked for access permissions (including
F_OK).
The real user ID is used in place of the effective user ID and the real group access list (including the real group ID) are used in place of
the effective ID for verifying permission.
If a process has super-user privileges and indicates success for R_OK or W_OK, the file may not actually have read or write permission bits
set. If a process has super-user privileges and indicates success for X_OK, at least one of the user, group, or other execute bits is set.
(However, the file may still not be executable. See execve(2).)
RETURN VALUES
If path cannot be found or if any of the desired access modes would not be granted, then a -1 value is returned; otherwise a 0 value is
returned.
ERRORS
Access to the file is denied if:
[EACCES] Permission bits of the file mode do not permit the requested access, or search permission is denied on a component of the
path prefix. The owner of a file has permission checked with respect to the ``owner'' read, write, and execute mode bits,
members of the file's group other than the owner have permission checked with respect to the ``group'' mode bits, and all
others have permissions checked with respect to the ``other'' mode bits.
[EFAULT] path points outside the process's allocated address space.
[EIO] An I/O error occurred while reading from or writing to the file system.
[ELOOP] Too many symbolic links were encountered in translating the pathname.
[ENAMETOOLONG] A component of a pathname exceeded {NAME_MAX} characters, or an entire path name exceeded {PATH_MAX} characters.
[ENOENT] The named file does not exist.
[ENOTDIR] A component of the path prefix is not a directory.
[EROFS] Write access is requested for a file on a read-only file system.
[ETXTBSY] Write access is requested for a pure procedure (shared text) file presently being executed.
SEE ALSO
chmod(2), execve(2), stat(2), secure_path(3)
STANDARDS
The access() function conforms to ISO/IEC 9945-1:1990 (``POSIX.1'').
SECURITY CONSIDERATIONS
The access() system call is a potential security hole due to race conditions. It should never be used. Set-user-ID and set-group-ID appli-
cations should restore the effective user or group ID, and perform actions directly rather than use access() to simulate access checks for
the real user or group ID.
The access() system call may however have some value in providing clues to users as to whether certain operations make sense for a particular
filesystem object. Arguably it also allows a cheaper file existence test than stat(2).
BSD
May 3, 2010 BSD