09-18-2002
My question on the file ownership changes.....since /dev/null permissions are set to rw-rw-rw and owned by bin, even if I change ownership over to root, wouldn't a process still be able to change the user level permissions on this device......to read only...and look like this afterwards, rw-rw-r--. since the user level permission is set to rw-.
thanks for the feedback...
OS
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi,
Q1-What does
nroff -ms > /dev/null
Q2- What does mean -A under STAT column :
ps aux |head -20
UTIL PID %CPU %MEM SZ RSS TTY STAT STIME TIME COMMAND
root 516 93,0 0,0 12 12 - A 04 nov 3906:51 wait
Thank you. (4 Replies)
Discussion started by: big123456
4 Replies
2. Shell Programming and Scripting
hello all,
In many shell scripts i found '> /dev/null' , i am not able to get this,
will any one please explain why we are using this.
thanks
sudha (2 Replies)
Discussion started by: rrs
2 Replies
3. Solaris
Hi, Anyone can help
My solaris 8 system has the following
/dev/null , /dev/tty and /dev/console
All permission are lrwxrwxrwx
Can this be change to a non-world write ??
any impact ?? (12 Replies)
Discussion started by: civic2005
12 Replies
4. Shell Programming and Scripting
Hi expert,
May I know what is the difference between below cron tab entry ?
0,12 * * * * /abc/myscript.sh > /dev/null 2>&1
0,12 * * * * /abc/myscript.sh (7 Replies)
Discussion started by: olaris
7 Replies
5. Shell Programming and Scripting
when do you use the path /dev/null (3 Replies)
Discussion started by: webmunkey23
3 Replies
6. UNIX for Dummies Questions & Answers
How are these two different? They both prevent output and error from being displayed. I don't see the use of the "&"
echo "hello" > /dev/null 2>&1
echo "hello" > /dev/null 2>1 (3 Replies)
Discussion started by: glev2005
3 Replies
7. Shell Programming and Scripting
I apologize if this question has been answered else where or is too elementary.
I ran across a KSH script (long unimportant story) that does this:
if ; then
CAS_SRC_LOG="/var/log/cas_src.log 2>&1"
else
CAS_SRC_LOG="/dev/null 2>&1"
fithen does this:
/usr/bin/echo "heartbeat:... (5 Replies)
Discussion started by: jbmorrisonjr
5 Replies
8. Shell Programming and Scripting
Hello All and a Happy New year to yous guys.
I'm running the below command on my AIX box and it keeps giving me the message that the file doesn't exist. I know the file don't exist, but I don't want to see the error. 2>/dev/null doesn't work.
bash-3.00$ ls -l C* | wc -l 2>/dev/null
ls:... (2 Replies)
Discussion started by: bbbngowc
2 Replies
9. AIX
Hi Experts,
I Have a query. In one of my server I just came to know that there was /dev/null file which is a not a character file. Its just a normal file. I know the command to create the character file (/dev/null) but what is the procedure. Like should i delete /dev/null and create or... (7 Replies)
Discussion started by: jayadeava
7 Replies
10. Shell Programming and Scripting
Friends have the following problem
a search may not find anything which would correct example:
ls -ltr *prueba.txt | nawk '{ print $9 }' > Procesar.dat 2>/dev/null
When he finds nothing gives me the following error
ls: prueba.txt: No such file or directory
because 2> / dev / null... (4 Replies)
Discussion started by: tricampeon81
4 Replies
LEARN ABOUT V7
logindevperm
logindevperm(4) File Formats logindevperm(4)
NAME
logindevperm, fbtab - login-based device permissions
SYNOPSIS
/etc/logindevperm
DESCRIPTION
The /etc/logindevperm file contains information that is used by login(1) and ttymon(1M) to change the owner, group, and permissions of
devices upon logging into or out of a console device. By default, this file contains lines for the keyboard, mouse, audio, and frame buffer
devices.
The owner of the devices listed in /etc/logindevperm is set to the owner of the console by login(1). The group of the devices is set to the
owner's group specified in /etc/passwd. The permissions are set as specified in /etc/logindevperm.
Fields are separated by TAB and/or SPACE characters. Blank lines and comments can appear anywhere in the file; comments start with a hash-
mark, ` # ', and continue to the end of the line.
The first field specifies the name of a console device (for example, /dev/console). The second field specifies the permissions to which the
devices in the device_list field (third field) will be set. These permissions must be expressed in octal format. For example, O774. A
device_list is a colon-separated list of device names. Note that a device name must be a /dev link. A device entry that is a directory
name and ends with "/*" specifies all entries in the directory (except "." and ".."). For example, "/dev/fbs/*" specifies all frame buffer
devices.
Once the devices are owned by the user, their permissions and ownership can be changed using chmod(1) and chown(1), as with any other user-
owned file.
Upon logout the owner and group of these devices will be reset by ttymon(1M) to owner root and root's group as specified in /etc/passwd
(typically other). The permissions are set as specified in the /etc/logindevperm file.
FILES
/etc/passwd File that contains user group information.
SEE ALSO
chmod(1), chown(1), login(1), ttymon(1M), passwd(4)
NOTES
/etc/logindevperm provides a superset of the functionality provided by /etc/fbtab in SunOS 4.x releases.
SunOS 5.10 22 Oct 2003 logindevperm(4)