02-09-2002
Quote:
Originally posted by shibz
Infact recently the hostname was changed. And that was done using uname -S.
Gack! That wasn't wise. The official Sun word is that you're supposed to use sys-unconfig which has a man page. The hostname is recorded in many places such as:
/etc/hostname.hme0 (or whatever you have for a network card)
/etc/nodename
and about 10 other files. I have used the sys-unconfig method ever since I got burnt doing it by hand.
And you should just ignore the TIME_WAITS. Each one goes away in a few minutes. They do not hurt performance.
8 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I have multiple Sun Solaris 8 systems running multiple network cards. (Mix of quad and gig cards.)
What I would like to do is create a monitor script to ensure high availability of these cards.
Has anyone ever had a situation like this?
I was thinking of using the ping command, but am... (1 Reply)
Discussion started by: Krusty
1 Replies
2. Solaris
I have need for a reliable and easy way to get from within a script, or a java class, the status of the network interface cards (whether the link is up, or down).
I believe the kernel status would be quicker to know if they were up or down rather than if a ping simply didnt respond back.
... (2 Replies)
Discussion started by: mrmurdock
2 Replies
3. AIX
Hello,
Is there any API or any other approach to detect whether the network cable is connected to the network adapter, say, en0, en1 or en2?
The OS is AIX6.1.
Thank you. (4 Replies)
Discussion started by: zephyrbj
4 Replies
4. AIX
Hi
I am currently testing SCOM2012 on my AIX systems for monitoring. I tested it on 3 systems and immediately i got the following errors:
Alert: Network Status Monitor daemon (rpcstat) is not running
Source: AIX 7.1
Path: (left blank)
Last modified by: (left blank)
Last modified time:... (3 Replies)
Discussion started by: jsabo40
3 Replies
5. Red Hat
Hi All,
RHEL4 on VM cannot get status network link down.
when I unplug network cable.
- ESX found interface down
- but VM RHEL4 not detect that !, It show still up (mii-tool)
Please help share you idea for my case.
ESXi 5.1.0, RHEL4
Thank you, (3 Replies)
Discussion started by: arm_naja
3 Replies
6. Shell Programming and Scripting
Actually I am using Red hat Linux 4.4 version.
I want to check the 16 client pc status of connection from server.Whether the connection is available or not.I tried to develop the shell script for this code.But It don't work properly.I am a self study learner.Please give me a shell script for this... (9 Replies)
Discussion started by: kannansoft1985
9 Replies
7. Solaris
I am again rephrasing the issue that we are facing:
We are creating link aggregations with two interfaces named net0 & net5:
# dladm create-aggr -m dlmp -l net0 -l net5 -l net2 aggr1
Setting prob targets for aggr1:
# dladm set-linkprop -p probe-ip=+ aggr1
Setting failure detection... (3 Replies)
Discussion started by: amitanshu.verma
3 Replies
8. Programming
Dear Team
I am using DB2 v10 z/os database . Need expert guidance to figure out best way to track table activities ( Ex Delete, Insert,Update )
Scenario
We have a table which is critical and many developer/testing team access on daily basis . We had instance where some deleted... (1 Reply)
Discussion started by: Perlbaby
1 Replies
LEARN ABOUT POSIX
systemd-socket-proxyd
SYSTEMD-SOCKET-PROXYD(8) systemd-socket-proxyd SYSTEMD-SOCKET-PROXYD(8)
NAME
systemd-socket-proxyd - Bidirectionally proxy local sockets to another (possibly remote) socket.
SYNOPSIS
systemd-socket-proxyd [OPTIONS...] HOST:PORT
systemd-socket-proxyd [OPTIONS...] UNIX-DOMAIN-SOCKET-PATH
DESCRIPTION
systemd-socket-proxyd is a generic socket-activated network socket forwarder proxy daemon for IPv4, IPv6 and UNIX stream sockets. It may be
used to bi-directionally forward traffic from a local listening socket to a local or remote destination socket.
One use of this tool is to provide socket activation support for services that do not natively support socket activation. On behalf of the
service to activate, the proxy inherits the socket from systemd, accepts each client connection, opens a connection to a configured server
for each client, and then bidirectionally forwards data between the two.
This utility's behavior is similar to socat(1). The main differences for systemd-socket-proxyd are support for socket activation with
"Accept=false" and an event-driven design that scales better with the number of connections.
OPTIONS
The following options are understood:
-h, --help
Print a short help text and exit.
--version
Print a short version string and exit.
--connections-max=, -c
Sets the maximum number of simultaneous connections, defaults to 256. If the limit of concurrent connections is reached further
connections will be refused.
EXIT STATUS
On success, 0 is returned, a non-zero failure code otherwise.
EXAMPLES
Simple Example
Use two services with a dependency and no namespace isolation.
Example 1. proxy-to-nginx.socket
[Socket]
ListenStream=80
[Install]
WantedBy=sockets.target
Example 2. proxy-to-nginx.service
[Unit]
Requires=nginx.service
After=nginx.service
Requires=proxy-to-nginx.socket
After=proxy-to-nginx.socket
[Service]
ExecStart=/lib/systemd/systemd-socket-proxyd /tmp/nginx.sock
PrivateTmp=yes
PrivateNetwork=yes
Example 3. nginx.conf
[...]
server {
listen unix:/tmp/nginx.sock;
[...]
Example 4. Enabling the proxy
# systemctl enable --now proxy-to-nginx.socket
$ curl http://localhost:80/
Namespace Example
Similar as above, but runs the socket proxy and the main service in the same private namespace, assuming that nginx.service has PrivateTmp=
and PrivateNetwork= set, too.
Example 5. proxy-to-nginx.socket
[Socket]
ListenStream=80
[Install]
WantedBy=sockets.target
Example 6. proxy-to-nginx.service
[Unit]
Requires=nginx.service
After=nginx.service
Requires=proxy-to-nginx.socket
After=proxy-to-nginx.socket
JoinsNamespaceOf=nginx.service
[Service]
ExecStart=/lib/systemd/systemd-socket-proxyd 127.0.0.1:8080
PrivateTmp=yes
PrivateNetwork=yes
Example 7. nginx.conf
[...]
server {
listen 8080;
[...]
Example 8. Enabling the proxy
# systemctl enable --now proxy-to-nginx.socket
$ curl http://localhost:80/
SEE ALSO
systemd(1), systemd.socket(5), systemd.service(5), systemctl(1), socat(1), nginx(1), curl(1)
systemd 237 SYSTEMD-SOCKET-PROXYD(8)