| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
So we use the standard method to find libraries.
|
|
|
|
| |
So we use the standard method to find libraries.
|
|
|
|
| |
So we use the standard method to find libraries.
|
|
|
|
| |
So we use the standard method to find libraries.
|
|\ |
|
| |
| |
| |
| |
| |
| | |
Fixes: https://issues.redhat.com/browse/RHEL-34880
Signed-off-by: Carlos Santos <casantos@redhat.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Return zero if the current argument starts with ":". It's useless to
check if it matches any of the other Xvnc arguments.
Also use the global variable explicit_display, set by the X server code,
instead of a private flag.
Signed-off-by: Carlos Santos <casantos@redhat.com>
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | | |
The kernel_read_fs_sysctls interface does exactly the same thing and we
don't reinvent the wheel. It's also easier to maintain.
|
| |/
|/|
| |
| |
| | |
Allow everything to flush properly so that both ends see a clean close,
rather than a reset connection. Avoids misleading error messages.
|
| |
| |
| |
| |
| | |
This was supposed to be removed in e97e225 when we moved this to the
core library.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This:
ret = vncHandleParamArg(argc, argv, i);
if (ret != 0)
return ret;
return 0;
Is the same as
return vncHandleParamArg(argc, argv, i);
Signed-off-by: Carlos Santos <casantos@redhat.com>
|
| |
| |
| |
| |
| |
| |
| | |
So it's not necessary to iterate over the internal list to obtain the
number of parameters.
Signed-off-by: Carlos Santos <casantos@redhat.com>
|
| |
| |
| |
| |
| |
| | |
The lifetime of this object was changed in b0c1dba, which resulted in
the object being destroyed immediately again. The server would then
crash on the next connection, where the invalid filter would be called.
|
|\ \ |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If we'll be running in inetd mode, then stdout and stderr will be a
client socket and not an appropriate place for logging.
Mimic what Xorg does instead.
|
| | | |
|
| | |
| | |
| | |
| | | |
Keep the compiler happy and get rid of noise.
|
| | |
| | |
| | |
| | |
| | | |
These things have been removed or moved to common code in Xorg 21.1, so
let's avoid it in our code to get rid of warnings.
|
| | | |
|
| | | |
|
|/ / |
|
|/
|
|
| |
This should have been done as part of cf1bc66.
|
|
|
|
|
| |
This is needed when the nofile limit is set to unlimited, otherwise we
will fail to start a VNC session.
|
|\ |
|
| |
| |
| |
| |
| |
| | |
There were not many uses of this left after the move to std::exception
and the move to the core library. Let's get rid of the last stragglers
and reduce the risk of name collisions.
|
| |
| |
| |
| |
| | |
To reduce the risk of duplicating the libraries on the link line, as we
have absolute paths in the .la files.
|
| |
| |
| |
| |
| | |
We should hopefully no longer require the common libraries to be linked
twice anymore for things to work.
|
| | |
|
| |
| |
| |
| |
| | |
OS abstractions are generic enough that we can merge these with the new
core library.
|
| |
| |
| |
| |
| | |
These are general plumbing, so they fit in nicely with the new core
library.
|
| |
| |
| |
| |
| | |
It's just string helper functions here, so let's get rid of the
catch-all name for this module.
|
| |
| |
| |
| |
| |
| |
| |
| | |
They weren't that well used, and were mostly just confusing special
functions anyway.
Allows us to move away from generic and ambigious headers such as
"util".
|
| |
| |
| |
| |
| |
| |
| | |
Make it clearer what is protocol handling and what is just general
plumbing.
This is one step of several.
|
| |
| |
| |
| |
| |
| |
| | |
Make it clearer what is protocol handling and what is just general
plumbing.
This is one step of several.
|
| |
| |
| |
| |
| |
| |
| | |
Make it clearer what is protocol handling and what is just general
plumbing.
This is one step of several.
|
| |
| |
| |
| |
| |
| |
| | |
Make it clearer what is protocol handling and what is just general
plumbing.
This is one step of several.
|
| |
| |
| |
| |
| |
| |
| | |
Make it clearer what is protocol handling and what is just general
plumbing.
This is one step of several.
|
| |
| |
| |
| |
| |
| |
| | |
Make it clearer what is protocol handling and what is just general
plumbing.
This is one step of several.
|
| |
| |
| |
| |
| |
| |
| |
| | |
Try to keep the code more compact for the simple things where the type
should be obvious from the context. Helps us avoid line wrapping.
Also remove explicit conversions to Region where the compiler is able to
figure it out by itself, again to reduce line length.
|
| |
| |
| |
| |
| | |
This is a network function, so it makes more sense in the network
library.
|
| |
| |
| |
| |
| | |
libtool seems to have some issues ordering everything correctly, and
this seems to work better.
|
| |
| |
| |
| |
| | |
Make compile times faster by reducing the number of headers included in
other headers.
|
|/
|
|
|
|
| |
We have policy that allows to create ~/.local or ~/.config, but we don't
have rule that allows the same under /root directory, where we fail in
case any of these directories doesn't exist.
|
|
|
|
|
| |
The argument index progression wasn't properly adjusted in e97e225,
causing it to skip arguments.
|
| |
|
| |
|
|
|
|
| |
It's not a formal name, so use regular case.
|
|
|
|
|
|
|
|
|
| |
Certain versions of the xserver code will crash if you access the
details of a disabled pointer. The details are also not up to date when
it is disabled, so it is likely concepually wrong to ignore it at this
point anyway.
Issue originally discovered and diagnosed by Mark Mielke.
|