11-16-2005
HPUX : identify NFS mountpoint
Is there a way to identify a directory as the start of an NFS mountpoint in HPUX 11.0? Using existing utilities & without root priv.
If you stat the directory and use the S_ISNWK macro you can find network special files that way. The requirement will have to go through other channels if I need to code a C routine to do this.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I am running HPUX and using WLM (workload manager). I want to write a script to fork CPUs to basically take CPUs from other servers to show that the communication is working and CPU licensing is working. Basically, I want to build a script that will use up CPU on a server. Any ideas? (2 Replies)
Discussion started by: cpolikowsky
2 Replies
2. HP-UX
I'm sharing this in case anybody needs it. Modified from the original solaris pwage script. This modified hpux script will check /etc/password file on hpux trusted systems search /tcb and grep the required u_succhg field. Calculate days to expiry and notify users via email.
original solaris... (2 Replies)
Discussion started by: sparcguy
2 Replies
3. Shell Programming and Scripting
Dear Guru's
Given a full filename /a/b/c/d/file.txt how do i determine what part is the mount point ( say /a/b).
Cheers, Karel (6 Replies)
Discussion started by: karelb
6 Replies
4. UNIX for Dummies Questions & Answers
Hello.
What's the best way to ensure that a NFS filesystem mounted from a disk-cabine (NAS) is accessible?
My proposal:
1. ping to the ip of the cabine
2. verify filesystem is mounted
3. touch a file inside the /mountpoint
Any other suggestions?
Thank you! (2 Replies)
Discussion started by: asanchez
2 Replies
5. UNIX for Advanced & Expert Users
Hello All,
I am new to System/plat-form administration work. Right now I am facing some issues while creating the filesystem and mounpoint. I am using Linux 6.0 SuSE 11. Last time I was used one command to partition the given space along with filesystem in SuSE 9 and it was done in GUI mode but... (0 Replies)
Discussion started by: nvkuriseti
0 Replies
6. Solaris
One of our mountpoint shows 100% but we have less data on that mountpoint. Pls help me to find which data/process holds the space.
bash-3.00$ cd /oracle/server_software/oracle10
bash-3.00$ du -sh *
0K admin
260M app
0K flash_recovery_area
0K lost+found
0K oradata
... (6 Replies)
Discussion started by: rock123
6 Replies
7. UNIX for Advanced & Expert Users
Can some one help me i try to mkfs new mountpoint from storageIBM but give some problem
# mkfs -t ext3 /dev/sdd1
mke2fs 1.39 (29-May-2006)
/dev/sdd1 is apparently in use by the system; will not make a filesystem here!
my os is redhat 5.3
using fdisk
# fdisk -l
Disk /dev/sda: 298.9... (4 Replies)
Discussion started by: vickyid04
4 Replies
8. AIX
root@atldc-oragrid-ux01:/oragrid_01> du -sg *
0.58 11gR2gridBase
47.31 Grid_11203
4.17 app
0.00 lost+found
0.01 oraInventory
root@atldc-oragrid-ux01:/oragrid_01> cd Grid_11203
root@atldc-oragrid-ux01:/oragrid_01/Grid_11203> du -sg *|sort
0.00 JRE
0.00 OPatch_old
0.00 ... (11 Replies)
Discussion started by: Vishal_dba
11 Replies
9. Shell Programming and Scripting
Hi,
I am new to shell scripting. I prepared a very simple script to monitor mount points but not geting desired output.
df -h|awk -F' ' '{ if ($5 >= 80) print "CRITICAL\n" $NF " mount point has reached " $5;}'|sed -n '3,$p'
When I run above script in Sun solaris box it is executing... (8 Replies)
Discussion started by: sv0081493
8 Replies
10. HP-UX
Hi.
I'm having problems with my HP C8000 and 11.11 (ifs client needs to be restarted every week), trying to get it worked out.
When I searched the web it seems, I require the following patches:
PHKL_41041, PHKL_43823, PHKL_43577
Is there anyway to get hold of these packages?
Many thanks... (2 Replies)
Discussion started by: plantage
2 Replies
LEARN ABOUT ULTRIX
fitset
fitset(8) System Manager's Manual fitset(8)
Name
fitset - determine if subset fits on a system
Syntax
fitset [ -d ] [ root-path ]
Description
The utility is used to determine if the files in a software subset will fit on a system.
Subset inventory records are read from the standard input. For each record, the space required to install the file described in that record
is deducted from the available free space on the file system to which it would be installed. Only currently mounted UFS file systems are
used in the computations. Space requirements for files already on the disk will be modified to account for the size of the resident copy.
After all records have been read, the free space computed for all file systems is checked. If the space required to install the files would
cause any file system to be more than 90% full, returns an exit status of -1.
The utility uses to size all subsets before attempting to install them. The root-path argument is the pathname of the top directory for
the hierarchy into which the files are going to be installed. If no root-path is specified, the directory '/' is assumed.
Options
-d Enable debugging. This will make print voluminous status information on standard output. This information is the initial file system
statistics, the file system location of the file from each input record and the statistics for the file system after the space
required to install the file has been deducted.
Restrictions
NFS mounts are ignored. If software would be installed to an NFS mounted directory, it is sized against the file system containing the NFS
mount point.
The program does not detect the use of symbolic links in paths to root-path or any of the mount points. This can cause to size a subset
incorrectly if root-path is a symbolic link or a symbolic link exists in the path of any of the pathnames used with the command to mount
local file systems.
Examples
To determine if a particular subset will fit on the system, redirect the contents of the subset inventory file into For example:
fitset < /usr/etc/subsets/ULTUUCP400.inv
To determine if the same subset will fit in a hierarchy rooted at the command would be:
fitset /var/tmp/root < /usr/etc/subsets/ULTUUCP400.inv
Diagnostics
fitset: root path must be absolute
A relative pathname was specified for root-path. This path must be absolute.
fitset: cannot stat root-path (error message)
The root-path cannot be accessed. The error message provides more information.
fitset: root-path is not a directory.
Either root-path is not a directory or it is a symbolic link to something which is not a directory.
Files
Subset inventory files
See Also
stl_inv(5), setld(8)
Guide to Preparing Software for Distribution on ULTRIX Systems
fitset(8)