It's been the go-to editor for your userbase for years, many people have based workflows around it and some maintain highly customized configs for it. When to use the alternatives commandĪ simple and realistic example: you have a command on your system called em, which launches a simple text editor. Red Hat rewrote the command without Perl, and it's been propagated throughout Fedora-based distributions such as Red Hat and CentOS, as well as other distributions that look to Red Hat for the functional definition of the Linux Standard Base (LSB).
Originally, this was a convenience utility, written in Perl, from the Debian Linux project, called update-alternatives. The alternatives command began its life as, interestingly, an alternative. Unless that is, you use the alternatives command. In theory, a Linux sysadmin can offer many system tools according to function rather than by the exact name of the executable, but that often requires a lot of symlinking and version tracking. In fact, even applications don't always care how something is achieved as long as all of its system calls are answered correctly.
Xscope linux alternative download#
One approach could be to use strace (or the equivalent command on your system if not Linux) to trace the send/receive system calls that your application does to communicate with the X server. Now, if you can't change $DISPLAY and want to capture the traffic of an already running local X application that uses unix domain sockets, that's where it gets tricky. You can then set $DISPLAY to localhost:4 and capture the network traffic as above or tell socat to dump it with -x -v. If it doesn't, you can use socat as a man in the middle that accepts connections as TCP and forwards them as unix or abstract: socat tcp-listen:6004,reuseaddr,fork unix:/tmp/.X11-unix/X4 If your X server listens on TCP (but they tend not to anymore nowadays), the easiest is to change DISPLAY to localhost:4 instead of :4 and capture the network traffic on port 6004 on the loopback interface.
Either /tmp/.X11-unix/X4 or the same path in the ABSTRACT namespace (usually shown as in netstat output). When $DISPLAY is only :4 (short for unix/:4), then clients use a unix domain socket. In that case, you can capture the traffic with any network sniffer like tcpdump or wireshark by capturing the TCP traffic on that port.
Xscope linux alternative plus#
The TCP port is then 6000 plus the display number (in that case 6004). When DISPLAY is set to host:4, short for tcp/host:4, clients use TCP to connect to the server.
You can talk X11 over TCP, or over a Unix domain socket or (on Linux) on a Unix domain socket in the abstract namespace.
0 kommentar(er)
