lxterminal in the netstat output
Can you explain the following lines in the netstat
output?
Can you explain the following lines in the netstat
output?
You can see the output from lscpu
command –
Could someone explain to me what a socket is? I see it in many acronyms in context of SSL, etc.
I’m running a Debian Squeeze web server. I’ve installed memcached on it, and configured memcached to listen on a Unix domain socket (at /tmp/memcached.sock
), as it only needs to receive messages from the website, which lives on the same server.
A vanilla ss -l
lists (on my current machine) lots of open sockets, with various Netid types and many of which are only listening on localhost.
I’m working on a software which connects to a Real Time data server (using TCP) and I have some connections dropping. My guess is that the clients do not read the data coming from the server fast enough. Therefore I would like to monitor my TCP sockets. For this I found the “ss” tool.
How do I reserve a list of ports for my custom applications?
I heard that FIFOs are named pipes. And they have exactly the same semantics. On the other hand, I think Unix domain socket is quite similar to pipe (although I’ve never made use of it). So I wonder if they all refer to the same implementation in Linux kernel. Any idea?
“Everything is a file” in the UNIX World.
When I run netstat --protocol unix
or lsof -U
I see that some unix socket paths are prepended with @ symbol, for example, @/tmp/dbus-qj8V39Yrpa. Then when I run ls -l /tmp
I don’t see file named dbus-qj8V39Yrpa there.