Javier Martinez <[email protected]> writes:
If you want, link Xwayland to X to see your needed X
process. Please
don't think that Xorg is a X called process, X usually is a link
to
Xorg, X11 or whatever be. Also please.... try to understand how
ps
works and what the comm is. The comm is just the name of the
executable and Xorg is not an X named process, is one server
that
talks the Xorg protocol, is Xnest a X windows server??? with
your
arguments not, because it's not called X, BUT IT'S an Xserver.
Oh, i meant to address this.
/usr/bin/X is indeed a symlink to /usr/bin/Xorg, at least on my
system:
$ ls -l /usr/bin/X
lrwxrwxrwx 1 root root 4 Jun 22 12:19 /usr/bin/X -> Xorg*
And that file is a binary:
$ file /usr/bin/Xorg
/usr/bin/Xorg: ELF 64-bit LSB pie executable, x86-64, version 1
(SYSV), dynamically linked, interpreter
/lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, stripped
However, the command line i provided in my post was:
# ps ax | grep X
where the `grep` is GNU grep, and will match _any_ instance of the
character 'X' in the process list, not just a process that's
literally nothing more than 'X'. That's why it listed Xwayland and
the grep process itself in the output:
3576 tty1 Sl+ 0:00 Xwayland :0 -rootless -core -terminate
-listenfd 26 -listenfd 27 -displayfd 67 -wm 64
12043 pts/21 S+ 0:00 grep --color=auto X
It would have also listed Xnest, had it been running.
That's how Basic Regular Expressions (BREs), as used by default by
GNU grep, work. If one wanted to match a literal 'X' and nothing
more, one would use the -F option to GNU grep, or fgrep, to
indicate that one doesn't want the pattern to be interpreted as an
RE, but as a fixed string.
Alexis.
