Sponsored Content
Operating Systems Linux How to easily identify socket given a PID on Linux? Post 302995446 by mohtashims on Wednesday 5th of April 2017 07:22:36 PM
Old 04-05-2017
Quote:
Originally Posted by DukeNuke2
I don't get this post... You say "Solaris" but the uname output says "Linux". And the question is posted in "Shell Programming and Scripting". Something is a little off here...

Can you change the title to Linux ? Solaris is a typo
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Session PID & socket connection pid

1. If I use an software application(which connects to the database in the server) in my local pc, how many PID should be registered? Would there be PID for the session and another PID for socket connection? 2. I noticed (through netstat) that when I logged in using the my software application,... (1 Reply)
Discussion started by: pcx26
1 Replies

2. UNIX for Dummies Questions & Answers

How to identify who rebooted the linux server

Hi All, Since server is located at remote place so how to identify which user rebooted the server. Is there any way to identify the user. Thanks in advance, Reg, Bache Gowda (1 Reply)
Discussion started by: bache_gowda
1 Replies

3. UNIX for Dummies Questions & Answers

how to find the owner PID of open socket on Solaris9?

Hi all, I am trying to connect the open socket and its owner PID on my Solaris9 system. But it seems not very easy. As netstat is not as powerful as it is on Linux platform, without the "-program" option, and "lsof -i <UDP|TCP>@<hostIP>" won't show the one i want although it lists some... (1 Reply)
Discussion started by: sleepy_11
1 Replies

4. Programming

Help needed linux socket programming in c

Good evening everyone! :) I'm doing a small client / server application for sharing files in C, and I am trying to implement the following: The client of my application sends to the address 255.255.255.255 a message requesting a particular file.In the network there is only one server,... (1 Reply)
Discussion started by: esmeco
1 Replies

5. Linux

how to identify the raid type on Linux?

Hi any idea on why I am getting this? /sbin/mdadm --detail /dev/md0 mdadm: md device /dev/md0 does not appear to be active. thanks. (2 Replies)
Discussion started by: melanie_pfefer
2 Replies

6. What is on Your Mind?

STILL can't buy a Linux PC easily

A few years ago, Dell announced they were selling PCs with Linux (Ubuntu) preinstalled or with no OS installed. It was about time! So a couple years ago I bought the Inspiron 1525n laptop that I'm typing this on with Ubuntu preinstalled. Yea! (Though I immediately wiped Ubuntu and installed... (7 Replies)
Discussion started by: KenJackson
7 Replies

7. UNIX for Advanced & Expert Users

Identify failed disk in Linux RAID

Good Evening, 2 years ago, I set up an Ubuntu file-server for a friend, who is a photograph amateur. Basically, the server offers a software RAID-5 that can be accessed remotely from a MAC. Unfortunately, I didn't labeled the hard drives (i.e. which physical drive corresponds to the /dev/sdX... (2 Replies)
Discussion started by: Loic Domaigne
2 Replies

8. IP Networking

Packets sent from Linux TCP socket

Hello, Our software is using a TCP socket (AF_INET, SOCK_STREAM) to communicate with an Ethernet device. When we send a message, the message object writes itself in full onto the socket's stream buffer before the software invokes send() from socket.h. I'm still researching, but have 2... (1 Reply)
Discussion started by: bix_20002000
1 Replies

9. Shell Programming and Scripting

Identify CPU usage on the Linux server

We are using linux server. We have below script running on the crontab and it send the alert if the cpu usage is above 90%. My question is, the below script tells the CPU usage for one CPU or all CPU in the server? sar 1 1 | sed '$!d' | awk '{printf("%d", $8)}' > $SAR_LOG Please let me... (4 Replies)
Discussion started by: govindts
4 Replies

10. UNIX for Dummies Questions & Answers

Need script for killing Pid in Linux

need script(shell or python) for killing pid in linux (2 Replies)
Discussion started by: roshan9995
2 Replies
re-preinstall(1M)					  System Administration Commands					 re-preinstall(1M)

NAME
re-preinstall - installs the JumpStart software on a system SYNOPSIS
cdrom-mnt-pt/Solaris_XX/Tools/Boot/usr/sbin/install.d/re-preinstall [-m Solaris_boot_dir] [-k platform_name] target-slice DESCRIPTION
re-preinstall installs the JumpStart software (preinstall boot image) on a system, so you can power-on the system and have it automatically install the Solaris software (perform a JumpStart installation on the system). When you turn on a re-preinstalled system, the system looks for the JumpStart software on the system's default boot disk. All new SPARC systems have the JumpStart software already preinstalled. The XX in Solaris_XX is the version number of the Solaris release being used. You can use the re-preinstall command in several ways. The most common way is to run re-preinstall on a system to install the JumpStart software on its own default boot disk. This is useful if you want to restore a system to its original factory conditions. (See the first procedure described in EXAMPLES.) You can also run re-preinstall on a system to install JumpStart software on any attached disk (non-boot disk). After you install the Jump- Start software on a disk, you can move the disk to a different system and perform a JumpStart installation on the different system. (See the second procedure described in EXAMPLES.) re-preinstall creates a standard file system on the specified target-slice (usually slice 0), and re-preinstall makes sure there is enough space on the target-slice for the JumpStart software. If sufficient space is not available, re-preinstall fails with the following message: re-preinstall: target-slice too small xx Megabytes required You can use the format(1M) command to create sufficient space on the target-slice for the JumpStart software. OPTIONS
The following options are supported: -k platform_name Platform name of the system that will use the disk with the JumpStart software. The default is the platform name of the system running re-preinstall. (Use the uname(1) command (-i option) to determine a system's platform name.) -m Solaris_boot_dir Absolute path to the Solaris_XX/Tools/Boot subdirectory of a mounted Solaris CD or a Solaris CD copied to disk that re-preinstall uses to install the JumpStart software. The default is root (/), which is where the Solaris CD is mounted in single-user mode. OPERANDS
The following operands are supported: target-slice Device name of the disk slice where the JumpStart software will be installed (usually slice 0), for example, c0t3d0s0. EXAMPLES
Example 1: Installing the JumpStart Software on a System's Own Default Boot Disk The following procedure installs the JumpStart software on a system's own default boot disk: 1. From the ok prompt, boot the system from the Solaris media CD or DVD in single-user mode: ok boot cdrom -s 2. The following command installs the Jumpstart software on the System default boot disk, c0t0d0s0 on a Solaris 9 system: example# /usr/sbin/install.d/re-preinstall c0t0d0s1 3. Reboot the slice: example# reboot disk:b Example 2: Installing the JumpStart Software on a System's Attached (non-boot) Disk The following procedure installs the JumpStart software on a system's attached (non-boot) disk: 1. Mount the Solaris CD or DVD if vold(1M) is not running or CD or DVD is not mounted. 2. Use the format(1M) command to determine the target-slice where JumpStart will be installed. 3. Use the uname(1) command (-i option) to determine the platform name of the system that will use the re-preinstalled disk 4. Run re-preinstall with the -m Solaris_boot_dir option if the Solaris CD or DVD is not mounted on /cdrom. The following command installs the JumpStart software on the system's attached disk for a system with a Sun4u kernel architecture, and it uses the Solaris CD or DVD mounted with vold(1M) on a Solaris 9 system: example# /cdrom/cdrom/s1/usr/bin/install.d/re-preinstall -m /cdrom/cdrom/s1 -k sun4u c0t2d0s0 EXIT STATUS
The following exit values are returned: 0 Successful completion. 1 An error has occurred. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcdrom (Solaris CD, | | |SPARC Platform Edition) | +-----------------------------+-----------------------------+ SEE ALSO
uname(1), eeprom(1M), format(1M), mount(1M), vold(1M), attributes(5) Solaris 10 Installation Guide: Basic Installations SunOS 5.10 9 Apr 2002 re-preinstall(1M)
All times are GMT -4. The time now is 04:21 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy