Hi,
In the following output you can see the the user "richard" is a member on the team/group "developers":
# id richard
uid=10247(richard) gid=100361(developers) groups=100361(developers),10053(testers)
but in the following details of the said group (developers), the said user... (3 Replies)
i have a directory like this:
i want to get the subpaths:
/home/user/public_html/a/b
subpath= a/b
/home/user/public_html/a/b/c
subpath= a/b/c
i can get the user like
echo $fulldirectory |awk -F/ '{print $3}'
but im not sure how to get the rest of it after public_html
any ideas?... (3 Replies)
How can I write a script that determines the directory the user is in, and displays that path up until a particular point?
Specifically, I need to find the text "packages" in the directory name, then I need to capture that directory and the one below it.
For example, if the user is in the... (5 Replies)
Hi,
Need awk help to group and print lines to format the output as shown below
INPUT FORMAT
set echo on
set heading on
set spool on
/* SCHEMA1 */ CREATE TABLE T1;
/* SCHEMA1 */ CREATE TABLE T2;
/* SCHEMA1 */ CREATE TABLE T3;
/* SCHEMA1 */ CREATE TABLE T4;
/* SCHEMA1 */ CREATE TABLE T5;... (5 Replies)
Hi,
A simple and silly question on Unix.
I have a directory named "a" and I would like to grant permission to group name "text" to access, read and execute my directory.
Could anyone help me?
Thanks. (2 Replies)
On my FTP server (Darwin/Mac OS X -- pretty much FreeBSD), I need to apply the following permissions to a directory:
1. A specific owner with full access
2. A specific group with full access
3. A specific group with read-only access
4. No access whatsoever for everyone else
I understand... (5 Replies)
MKDIR(2) Linux Programmer's Manual MKDIR(2)NAME
mkdir - create a directory
SYNOPSIS
#include <sys/stat.h>
#include <sys/types.h>
int mkdir(const char *pathname, mode_t mode);
DESCRIPTION
mkdir() attempts to create a directory named pathname.
The argument mode specifies the permissions to use. It is modified by the process's umask in the usual way: the permissions of the created
directory are (mode & ~umask & 0777). Other mode bits of the created directory depend on the operating system. For Linux, see below.
The newly created directory will be owned by the effective user ID of the process. If the directory containing the file has the set-group-
ID bit set, or if the file system is mounted with BSD group semantics (mount -o bsdgroups or, synonymously mount -o grpid), the new direc-
tory will inherit the group ownership from its parent; otherwise it will be owned by the effective group ID of the process.
If the parent directory has the set-group-ID bit set then so will the newly created directory.
RETURN VALUE
mkdir() returns zero on success, or -1 if an error occurred (in which case, errno is set appropriately).
ERRORS
EACCES The parent directory does not allow write permission to the process, or one of the directories in pathname did not allow search per-
mission. (See also path_resolution(7).)
EEXIST pathname already exists (not necessarily as a directory). This includes the case where pathname is a symbolic link, dangling or
not.
EFAULT pathname points outside your accessible address space.
ELOOP Too many symbolic links were encountered in resolving pathname.
EMLINK The number of links to the parent directory would exceed LINK_MAX.
ENAMETOOLONG
pathname was too long.
ENOENT A directory component in pathname does not exist or is a dangling symbolic link.
ENOMEM Insufficient kernel memory was available.
ENOSPC The device containing pathname has no room for the new directory.
ENOSPC The new directory cannot be created because the user's disk quota is exhausted.
ENOTDIR
A component used as a directory in pathname is not, in fact, a directory.
EPERM The file system containing pathname does not support the creation of directories.
EROFS pathname refers to a file on a read-only file system.
CONFORMING TO
SVr4, BSD, POSIX.1-2001.
NOTES
Under Linux apart from the permission bits, only the S_ISVTX mode bit is honored. That is, under Linux the created directory actually gets
mode (mode & ~umask & 01777). See also stat(2).
There are many infelicities in the protocol underlying NFS. Some of these affect mkdir().
SEE ALSO mkdir(1), chmod(2), chown(2), mkdirat(2), mknod(2), mount(2), rmdir(2), stat(2), umask(2), unlink(2), path_resolution(7)COLOPHON
This page is part of release 3.27 of the Linux man-pages project. A description of the project, and information about reporting bugs, can
be found at http://www.kernel.org/doc/man-pages/.
Linux 2010-06-26 MKDIR(2)