02-26-2013
lsof is pretty system-independent once you have one for each system. If you have multiple IP server sockets can be listened on 0.0.0.0 (all), 127.0.0.1 (localhost only)or any of those addresses, which would have different host.domain names.
In practice, usually one server listening on 0.0.0.0 splits connections on multiple virtual server file trees based on the http header host.domain name. The host can have one IP with many DNS CNAME host.domain names that resolve to it. Browsers putting that IP in the URL or running on the server host using 127.0.0.1 will get the default virtual host.domain web service.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello,
Please help me to know, How to find out the how much amount of process addres space is required/is used for/by a process.
Tnx & Regards
Vishwa. (1 Reply)
Discussion started by: S.Vishwanath
1 Replies
2. UNIX for Dummies Questions & Answers
Hi all,
How can I log all requests on ports for programs like ftp, telnet, rsh, xdmcp etc...
I want to see if anyone uses these programs/protocols and how often.
Is it difficult to setup a log for these ports and listen on all requests?
/combat (4 Replies)
Discussion started by: tonlu
4 Replies
3. Programming
Hi,
I am looking to work on unix systems which include (hp-ux, ibm aix, solaris and linux). I want to get the total virtual address space of a process, the used virtual memory i am able to get without any problem. I have tried using getrlimit and getrlimit64, but that gives only ... (4 Replies)
Discussion started by: uiqbal
4 Replies
4. UNIX for Advanced & Expert Users
Can kernel process access user address space ? (2 Replies)
Discussion started by: subhotech
2 Replies
5. UNIX for Dummies Questions & Answers
hi,
For some special reason , I'd like to control the memory address for the shared libraries in my dynamically linked process.
And it is the "ld" which interpret the dynamically linked library, and in my system, the "ld-linux.so.2" is put at 0x00812000. Then I use "prelink -r" command to change... (0 Replies)
Discussion started by: zerocool_08
0 Replies
6. Linux
hi,
For some special reason , I'd like to control the memory address for the shared libraries in my dynamically linked process.
And it is the "ld" which interpret the dynamically linked library, and in my system, the "ld-linux.so.2" is put at 0x00812000. Then I use "prelink -r" command to... (3 Replies)
Discussion started by: zerocool_08
3 Replies
7. Programming
Hi All,
From C++, I just want to find the address space size that a process is allowed to use. For ex, in 32 bit OS the allowed address space is 4GB and in 64 bit OS I guess this is 16GB or more.
I jsut want to find it in my C++ project. Is there any API calls that gives me such information.... (2 Replies)
Discussion started by: Sendil Kumar
2 Replies
8. Solaris
Hi
If suppose there is a MAC address of NIC port. I have change the MAC address through following command
# ifconfig hme0 ether a:0:30:f0.ad:51
The change MAC address will be there till reboot.
Now I would like to know how to make the change MAC address permanent. I believe that... (1 Reply)
Discussion started by: amity
1 Replies
9. IP Networking
Hi,
I am trying to configure a transparent squid cache. When I try to use the below option in squid.conf, squid listens on port 80 only for the IP address configured on the system's interface.
http_port 80 transparent
But I want squid to accept connections for any IP address on port 80.... (3 Replies)
Discussion started by: Learner32
3 Replies
10. Programming
Suppose I have 3 gb of ram and 250 gb hard disk in my pc.
Now I wrote a simple C program having only one statement malloc() to allocate 4 gb of memory as 32 bit os can address 4gb address space then will the malloc succeed?
If yes then how it will get extra 1 gb of memory?
Does the process gets... (3 Replies)
Discussion started by: rupeshkp728
3 Replies
LEARN ABOUT MOJAVE
systemd-socket-activate
SYSTEMD-SOCKET-ACTIVATE(1) systemd-socket-activate SYSTEMD-SOCKET-ACTIVATE(1)
NAME
systemd-socket-activate - Test socket activation of daemons
SYNOPSIS
systemd-socket-activate [OPTIONS...] daemon [OPTIONS...]
DESCRIPTION
systemd-socket-activate may be used to launch a socket-activated service program from the command line for testing purposes. It may also be
used to launch individual instances of the service program per connection.
The daemon to launch and its options should be specified after options intended for systemd-socket-activate.
If the --inetd option is given, the socket file descriptor will be used as the standard input and output of the launched process.
Otherwise, standard input and output will be inherited, and sockets will be passed through file descriptors 3 and higher. Sockets passed
through $LISTEN_FDS to systemd-socket-activate will be passed through to the daemon, in the original positions. Other sockets specified
with --listen= will use consecutive descriptors. By default, systemd-socket-activate listens on a stream socket, use --datagram and
--seqpacket to listen on datagram or sequential packet sockets instead (see below).
OPTIONS
-l address, --listen=address
Listen on this address. Takes a string like "2000" or "127.0.0.1:2001".
-a, --accept
Launch an instance of the service program for each connection and pass the connection socket.
-d, --datagram
Listen on a datagram socket (SOCK_DGRAM), instead of a stream socket (SOCK_STREAM). May not be combined with --seqpacket.
--seqpacket
Listen on a sequential packet socket (SOCK_SEQPACKET), instead of a stream socket (SOCK_STREAM). May not be combined with --datagram.
--inetd
Use the inetd protocol for passing file descriptors, i.e. as standard input and standard output, instead of the new-style protocol for
passing file descriptors using $LISTEN_FDS (see above).
-E VAR[=VALUE], --setenv=VAR[=VALUE]
Add this variable to the environment of the launched process. If VAR is followed by "=", assume that it is a variable-value pair.
Otherwise, obtain the value from the environment of systemd-socket-activate itself.
--fdname=NAME[:NAME...]
Specify names for the file descriptors passed. This is equivalent to setting FileDescriptorName= in socket unit files, and enables use
of sd_listen_fds_with_names(3). Multiple entries may be specifies using separate options or by separating names with colons (":") in
one option. In case more names are given than descriptors, superfluous ones will be ignored. In case less names are given than
descriptors, the remaining file descriptors will be unnamed.
-h, --help
Print a short help text and exit.
--version
Print a short version string and exit.
ENVIRONMENT VARIABLES
$LISTEN_FDS, $LISTEN_PID, $LISTEN_FDNAMES
See sd_listen_fds(3).
$SYSTEMD_LOG_TARGET, $SYSTEMD_LOG_LEVEL, $SYSTEMD_LOG_COLOR, $SYSTEMD_LOG_LOCATION
Same as in systemd(1).
EXAMPLES
Example 1. Run an echo server on port 2000
$ systemd-socket-activate -l 2000 --inetd -a cat
Example 2. Run a socket-activated instance of systemd-journal-gatewayd(8)
$ systemd-socket-activate -l 19531 /lib/systemd/systemd-journal-gatewayd
SEE ALSO
systemd(1), systemd.socket(5), systemd.service(5), sd_listen_fds(3), sd_listen_fds_with_names(3), cat(1)
systemd 237 SYSTEMD-SOCKET-ACTIVATE(1)