11-16-2010
It's FreeBSD 7.1 & program is a C binary.
The earlier permissions are 555
Good User:
ls -lisad Test
2361939 8 -r-xr-xr-x 1 A B 5524 Nov 16 16:14 Test
df -k .
Filesystem 1024-blocks Used Avail Capacity Mounted on
bng-enghomes001-cf2-2:/vol/home2/homes2 335544320 278167232 57377088 83% /.amd/bng-enghomes001-cf2-2/vol/home2/homes2
Bad User:
ls -lisad Test
27945903 8 -r-xr-xr-x 1 C D 5524 Nov 16 16:13 Test
df -k .
Filesystem 1024-blocks Used Avail Capacity Mounted on
bng-enghomes001-cf1-5:/vol/home5/homes5 880803840 653956752 226847088 74% /.amd/bng-enghomes001-cf1-5/vol/home5/homes5
Figured out something:
It has something to do with the underlying permissions.
In directory where good user was successful, bad user was as well
And where bad user was unsuccessful, good was unsuccessful as well
Can somebody help me enterpret these filesystem permissions.
I don't have much knowledge of this.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
hey all, I guess I'm the newbie on these boards, anyways, hello.
I recently became the admin for a few Solaris machines, and I have recently discovered an issue with SSH on one of my machines.
On one of my machines, I can only SSH into the machine as root. I have tried the newest version... (6 Replies)
Discussion started by: AKM
6 Replies
2. UNIX for Advanced & Expert Users
OK so i have a virtual server where i store files. one day i tied to login and i couldn't connect to my sevrer so i logged into my ssh and checked to see if the process was running. proftp was not. I then tried to start it manually and got the error below. Now the domain listed there is not mine... (2 Replies)
Discussion started by: thirddegreekris
2 Replies
3. UNIX for Advanced & Expert Users
Hi All,
a bit of a weird one here. I'm trying to pass a variable into an awk command, and I keep getting an error.
I have the line
nawk -F"," -v red=$random_variable '{print $red}' $w_dir/$file_name > $w_dir/${column_name}
that keeps failing with the error
nawk: can't open file {print... (17 Replies)
Discussion started by: Khoomfire
17 Replies
4. HP-UX
Hello all,
Normally I'm pretty comfortable with crontab, changing and updating (done it many-a-time).
But in the last two days I've been pulling my hair out over the following...
Details of OS:
HP-UX mdirect B.11.23 U ia64 2587410573 unlimited-user license
Issue:
Execute a script (very... (3 Replies)
Discussion started by: Cameron
3 Replies
5. Shell Programming and Scripting
I have a file called merge2.t:
Hi
Hello how are you.
</Endtag> <New> I am fine.</New>
This is a test.
freelong
how
Here is the SED:
sed -n ' /<\/Endtag>/ !{
H
}
/<\/Endtag>/ {
x
p
} (4 Replies)
Discussion started by: freelong
4 Replies
6. AIX
We recently upgraded 2 of our AIX 6.1 servers from TL4 to TL5.
Both servers are on the same p7 780 frame, installed at the same time from the same image. Both servers are mounting the same nfs share after reboot what worked perfectly fine until the upgrade.
Since the patching, one of the two... (5 Replies)
Discussion started by: zxmaus
5 Replies
7. Shell Programming and Scripting
I run this
#!/bin/bash
cron=$(ps aux | grep crond | grep -v grep | grep -o crond| uniq)
echo "cron :$cron:"
if ; then
echo "OK: crond service running fine on `hostname`"
exit 2
else
echo "CRITICAL: crond service not running on `hostname`"
exit 0... (2 Replies)
Discussion started by: anil510
2 Replies
8. Shell Programming and Scripting
Hi Guys,
I have used Perl scripting to convert XLSX file to TXT file using Perl module Spreadsheet::XLSX.
I processed one XLSX file having one column and 65k rows of data .
Strangely ,It is merging data for every 2047 row and I could see data in TXT file as Ex: Suppose in XLSX file ,if... (2 Replies)
Discussion started by: Rajk459
2 Replies
9. UNIX for Dummies Questions & Answers
Hey guys,
Suppose i run passwd via bash shell. It is a suid program, which temporarily runs as root(owner) and modifies the user entries.
However, when i write a C file and give 4755 permission and root ownership to the 'a.out' file , it doesn't run as root in bash shell. I verified this by... (2 Replies)
Discussion started by: syncmaster
2 Replies
10. UNIX for Beginners Questions & Answers
HI Team -
I'm running into a weird issue when trying to call a .ksh script.
In my shell script, I'm using the following command to call my environment file:
cd /hypbin/test
./_env.ksh
But it's saying not found. Permissions are set correctly, shebang is set but I'm unsure why it's not... (5 Replies)
Discussion started by: SIMMS7400
5 Replies
volfs(7FS) File Systems volfs(7FS)
NAME
volfs - Volume Management file system
DESCRIPTION
volfs is the Volume Management file system rooted at root_dir. The default location for root-dir is /vol, but this can be overridden using
the -d option of vold (see vold(1M)). This file system is maintained by the Volume Management daemon, vold, and will be considered to be
/vol for this description.
Media can be accessed in a logical manner (no association with a particular piece of hardware), or a physical manner (associated with a
particular piece of hardware).
Logical names for media are referred to through /vol/dsk and /vol/rdsk. /vol/dsk provides block access to random access devices. /vol/rdsk
provides character access to random access devices.
The /vol/rdsk and /vol/dsk directories are mirrors of one another. Any change to one is reflected in the other immediately. The dev_t for a
volume will be the same for both the block and character device.
The default permissions for /vol are mode=0555, owner=root, group=sys. The default permissions for /vol/dsk and /vol/rdsk are mode=01777,
owner=root, group=sys.
Physical references to media are obtained through /vol/dev. This hierarchy reflects the structure of the /dev name space. The default per-
missions for all directories in the /vol/dev hierarchy are mode=0555, owner=root, group=sys.
mkdir(2), rmdir(2), unlink(2) (rm), symlink(2) (ln -s), link(2) (ln), and rename(2) (mv) are supported, subject to normal file and direc-
tory permissions.
The following system calls are not supported in the /vol filesystem: creat(2), only when creating a file, and mknod(2).
If the media does not contain file systems that can be automatically mounted by rmmount(1M), users can gain access to the media through the
following /vol locations:
+-----------------------------------+------------------------------------+
| Location | State of Media |
+-----------------------------------+------------------------------------+
|/vol/dev/diskette0/unnamed_floppy | formatted unnamed floppy-block |
| | device access |
+-----------------------------------+------------------------------------+
|/vol/dev/rdiskette0/unnamed_floppy | formatted unnamed floppy-raw |
| | device access |
+-----------------------------------+------------------------------------+
|/vol/dev/diskette0/unlabeled | unlabeled floppy-block device |
| | access |
+-----------------------------------+------------------------------------+
|/vol/dev/rdiskette0/unlabeled | unlabeled floppy-raw device access |
+-----------------------------------+------------------------------------+
|/vol/dev/dsk/c0t6/unnamed_cdrom | CD-ROM-block device access |
+-----------------------------------+------------------------------------+
|/vol/dev/rdsk/c0t6/unnamed_cdrom | CD-ROM-raw device access |
+-----------------------------------+------------------------------------+
For more information on the location of CD-ROM and floppy media, see System Administration Guide: Basic Administration or rmmount(1M).
Partitions
Some media support the concept of a partition. If the label identifies partitions on the media, the name of the media becomes a directory
with partitions under it. Only valid partitions are represented. Partitions cannot be moved out of a directory.
For example, if disk volume 'foo' has three valid partitions, 0, 2, and 5, then:
/vol/dsk/foo/s0
/vol/dsk/foo/s2
/vol/dsk/foo/s5
for block access and
/vol/rdsk/foo/s0
/vol/rdsk/foo/s2
/vol/rdsk/foo/s5
for character access.
If a volume is relabeled to reflect different partitions, the name space changes to reflect the new partition layout.
A format program can check to see if there are others with the volume open and not allow the format to occur if it is. Volume Management,
however, does not explicitly prevent the rewriting of a label while others have the volume open. If a partition of a volume is open, and
the volume is relabeled to remove that partition, it will appear exactly as if the volume were missing. A notify event will be generated
and the user may cancel the operation with volcancel(1), if desired.
SEE ALSO
volcancel(1), volcheck(1), volmissing(1) rmmount(1M), vold(1M), rmmount.conf(4), vold.conf(4)
System Administration Guide: Basic Administration
SunOS 5.10 8 Feb 1995 volfs(7FS)