Whenever I create a new file the group name is "dnn" and the file permissions are "-rw-r--r--".
How do I get it so when I create files (with vi or other programs) that the default group is "sss" and the permissions are 770?
(I am running HP-UNIX)
Thanks,
GoldFish (2 Replies)
folks;
I created a new users on my SUSE box and i need to give this user/group a read write access to one specific folder. here's the details:
- I created new user "funny" under group "users".
- I need to give this user "funny" a read/write access to another directory that is owned by "root".... (3 Replies)
Hi,
We have smb client running on two of the linux boxes and smb server on another linux system. During a backup operation which uses smb, read of a file was allowed while write to the same file was going on.Also simultaneous writes to the same file were allowed.Following are the settings in the... (1 Reply)
I know this may sound little incomplete but this is what i read on some linux hardening guide.I dont have any clue on how to remove group's write bit.
I m posting the exact sentence of the hardening guide.
What all system files to be taken care of?
---------- Post updated 10-04-10 at... (3 Replies)
How would i write a command that can find all the objects under the etc directory that have group write permission enabled and have not been accessed in the last X days.
This is what i got from internet souce but i m not able to modify it according to my distribution.
find /etc -perm... (1 Reply)
Guys, i wanna get any user files with write permission (on user or group permission) for review but i confuse with -perm parameter.
any body can help me to explain what is that mean?
thank's (1 Reply)
In our project we have several unix scripts that trigger different processes. These scripts write logs to a particular folder 'sesslogs', create output data files in a separate directory called 'datafiles' etc. Usually L1 support team re-run these scripts . We donot want L1 support team to have... (14 Replies)
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)
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. This is for Solaris. Please help. (1 Reply)
Discussion started by: blinkingdan
1 Replies
LEARN ABOUT HPUX
mkfifo
mkfifo(3C)mkfifo(3C)NAME
mkfifo() - make a FIFO file
SYNOPSIS DESCRIPTION
creates a new FIFO (first-in-first-out) file, at the path name to which path points. The file permission bits of the new file are initial-
ized from the mode argument, as modified by the process's file creation mask: for each bit set in the process's file mode creation mask,
the corresponding bit in the new file's mode is cleared (see umask(2)). Bits in mode other than the file permission bits are ignored.
The FIFO owner ID is set to the process's effective-user-ID. The FIFO group ID is set to the group ID of the parent directory if the set-
group-ID bit is set on that directory. Otherwise the FIFO group ID is set to the process's effective group ID.
For details of the I/O behavior of pipes see read(2) and write(2).
The following symbolic constants are defined in the header, and should be used to construct the value of the mode argument. The value
passed should be the bitwise inclusive OR of the desired permissions:
Read by owner.
Write by owner.
Read by group.
Write by group.
Read by other users.
Write by other users.
RETURN VALUE
returns 0 upon successful completion. Otherwise, it returns -1, no FIFO is created, and is set to indicate the error.
ERRORS
fails and the new file is not created if any of the following conditions are encountered:
[EACCES] A component of the path prefix denies search permission.
[EEXIST] The named file already exists.
[EFAULT] The path argument points outside the process's allocated address space. The reliable detection of this error is
implementation dependent.
[ELOOP] Too many symbolic links encountered in translating the path name.
[ENAMETOOLONG] 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.
[ENOENT] A component of the path prefix does not exist.
[ENOENT] The path argument is null.
[ENOSPC] Not enough space on the file system.
[ENOTDIR] A component of the path prefix is not a directory.
[EROFS] The directory in which the file is being created is located in a read-only file system.
AUTHOR
was developed by HP.
SEE ALSO chmod(2), mknod(2), pipe(2), stat(2), umask(2), mknod(5), stat(5), thread_safety(5), types(5).
STANDARDS CONFORMANCE mkfifo(3C)