Sponsored Content
Full Discussion: /tmp issue on solaris10 box
Operating Systems Solaris /tmp issue on solaris10 box Post 302408920 by fugitive on Tuesday 30th of March 2010 10:28:49 PM
Old 03-30-2010
Thanx i got the info from prstat -a -s size .. and got to know which zone is using the max swap space ..
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

monitoring /tmp and /var/tmp for suspicous activity

Hello, does anyone have a script that can check the contents of the /tmp directory and for example e-mail the directory content if anything other than session files are present? Maybe there are better ways to monitor suspicous /tmp and /var/tmp activity, if so I'm listening :) (1 Reply)
Discussion started by: jamesbond
1 Replies

2. Shell Programming and Scripting

portability issue linux(2.6) solaris10

the following simple scripts work fine on linux but fail on solaris: #!/bin/bash eval /usr/bin/time -f \'bt=\"%U + %S\"\' ./JUNK >> ./LOG 2>&1 cp ./LOG ./LOG_joe LC_joe=`cat ./LOG | wc -l` LC_joe=`echo $LC_joe-1|bc` tail -1 ./LOG > ./tmp head -$LC_joe ./LOG_joe > ./LOG rm ./LOG_joe ... (1 Reply)
Discussion started by: joepareti
1 Replies

3. Shell Programming and Scripting

issue a ping on a remote box

Hi there I am running a script on a central box (boxA) that will send a remote request to boxB to perform a ping test to an ip note: I am not pinging boxB from boxA but sending a request over ssh to get boxB to perform a ping test ! The thing is, I want the script back at boxA to know... (4 Replies)
Discussion started by: hcclnoodles
4 Replies

4. Shell Programming and Scripting

Issue with a sed one liner variant - sed 's/ ; /|/g' $TMP1 > $TMP

Execution of the following segment is giving the error - Script extract:- OUT=$DATADIR/sol_rsult_orphn.bcp TMP1=${OUT}_tmp1 TMP=${OUT}_tmp ( isql -w 400 $dbConnect_OPR <<EOF select convert(char(10), s.lead_id) +'|' + s.pho_loc_type, ";", s.sol_rsult_cmnt, ";", +'|'+ s.del_ind... (3 Replies)
Discussion started by: kzmatam
3 Replies

5. Solaris

Issue with box not powering on

Hi, I'm having an issue with a SunFire X4140 with it not powering on. I just want to see if anyone has any ideas on what is causing this before I give up and put it down to hardware failure. I upgraded the iLOM firmware to version 3.0.37a. The following are my actions after the firmware upgrade.... (3 Replies)
Discussion started by: Chains
3 Replies

6. Solaris

Memory issue on solaris10 box

my system has 128G of installed memory. top, vmstat shows the system has just over 10G of free memory on the system. but as per prstat o/p the usage is just 50-55G is there anyway i can find which process/zone is using more memory ? System has 3 zones and all running application servers. ... (1 Reply)
Discussion started by: fugitive
1 Replies

7. Solaris

Swap issue on a Solaris10 box

One of our system is running 3 oracle db instances. And as per prstat o/p the system is approximately using 78G of swap memory # prstat -J -n 2,15 PROJID NPROC SWAP RSS MEMORY TIME CPU PROJECT 4038 557 31G 29G 22% 113:23:43 10% proj1 4036 466 20G 19G... (2 Replies)
Discussion started by: fugitive
2 Replies

8. Solaris

VNC issue on solaris10

M running solaris 10 u8 my vncserver is running on :0 .. and when i try to connect it through tight vncview i can see just see the screen .. with no terminal .. what could be the issue for it ? and what i need to check for it ? (2 Replies)
Discussion started by: fugitive
2 Replies

9. Solaris

Veritas I/O fencing issue on Solaris10

I have 2 clusters running on solaris10 servers. VCS is working fine but when i configure I/O fencing with co-ordinated disks only one node have the keys on the disks at time where as both the nodes shuld have keys there what could be the reason for this ? like in the following o/p only Node2's... (0 Replies)
Discussion started by: fugitive
0 Replies

10. Shell Programming and Scripting

Issue with rsync: failed to set times on "/tmp/.": Not owner (1)

Hi, Here is my source host and folder details. $ hostname source-host $ id uid=600000208(src-user) gid=64688(src-user) groups=64688(src-user) $ ls -ltrd /web/Trn_File/data/ drwxrwxrwx 3 src-user src-user 4096 Feb 7 15:27 /web/Trn_File/data/ $ ls -ltrd /web/Trn_File/data/* drwxrwxrwx 8... (1 Reply)
Discussion started by: mohtashims
1 Replies
info(4) 						     Kernel Interfaces Manual							   info(4)

NAME
info - diskless client configuration information file DESCRIPTION
The file is a POSIX shell sourceable file which contains parameter definitions used at boot time. Typically, it will be an empty file and default values will be used for all parameters. Following is the list of parameters which can be defined in the file: Specifies the IP address of the client's private root server. If this is not specified, the client's private root server defaults to the boot server. Specifies the pathname to the client's private root on the private root server. If this is not specified, the client's private root path defaults to Specifies the NFS mount options to mount the client's private root from the private root server. If this is not specified, the mount options default to Specifies the NFS mount options to mount the client's directory from the boot server. If this is not specified, the mount options default to Specifies whether NFS should be configured as primary swap. (NOTE: In order to swap to NFS, a diskless kernel must be configured with tunable parameter set to 1.) If a diskless machine has a local swap disk and swap to NFS is not desired, the parameter should be set to the value of 1 and the diskless kernel should be configured without setting to 1. If this parameter is not specified in the file and the kernel tunable parameter is set to 1, then NFS will be configured as primary swap. If not set, this parameter defaults to a value of 1, and results in the removal of all swapfiles above the configured swap minimum (swap is specified in the client's when a disk- less client boots. This ensures that extraneous swapfiles at boot time are removed, thus freeing disk space. If is set to 0 in the file, removal of extra swapfiles is disabled. This may result in faster boot times due to the time savings in creating additional swap files. The file resides in the same directory as the client's kernel () on the boot server and is retrieved at boot time using command. By default, when a diskless client is created, an empty file is placed in the client's kernel directory. This ensures that all parameters revert to their default values (see above). If the file is not present, this is an error. EXAMPLES
An example file is shown below: FILES
info(4)
All times are GMT -4. The time now is 06:10 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy