Web lists-archives.com

Re: [PATCH xpdf] Add desktop menu entry

On 2017-10-28 12:00, Ken Brown wrote:
> On 10/27/2017 5:00 PM, Yaakov Selkowitz wrote:
>> ---
>>   xpdf.cygport | 4 ++++
>>   1 file changed, 4 insertions(+)
> After making this change I get the following warning when starting xpdf in an
> xterm window:
> QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kbrown'
> I googled the message, but none of the solutions appeared to apply.  Do you know
> how to suppress this warning?  I assume it results from the fact that I'm not
> working in a desktop environment.

Normally set to /run/user/$(id -u)/, sometimes .../$(id -un)/, created by first
app after login.
I have a postinstall script to create /run/{,blkid,lock,user}/ directories with
mode a+rwxt, remove /var/{run,lock} directories and create symlinks from those
to /run/{,lock}/, to provide a more normal Unix/Linux environment for ported apps.

>From https://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html:

"$XDG_RUNTIME_DIR defines the base directory relative to which user-specific
non-essential runtime files and other file objects (such as sockets, named
pipes, ...) should be stored. The directory MUST be owned by the user, and he
MUST be the only one having read and write access to it. Its Unix access mode
MUST be 0700.

The lifetime of the directory MUST be bound to the user being logged in. It MUST
be created when the user first logs in and if the user fully logs out the
directory MUST be removed. If the user logs in more than once he should get
pointed to the same directory, and it is mandatory that the directory continues
to exist from his first login to his last logout on the system, and not removed
in between. Files in the directory MUST not survive reboot or a full
logout/login cycle.

The directory MUST be on a local file system and not shared with any other
system. The directory MUST by fully-featured by the standards of the operating
system. More specifically, on Unix-like operating systems AF_UNIX sockets,
symbolic links, hard links, proper permissions, file locking, sparse files,
memory mapping, file change notifications, a reliable hard link count must be
supported, and no restrictions on the file name character set should be imposed.
Files in this directory MAY be subjected to periodic clean-up. To ensure that
your files are not removed, they should have their access time timestamp
modified at least once every 6 hours of monotonic time or the 'sticky' bit
should be set on the file.

If $XDG_RUNTIME_DIR is not set applications should fall back to a replacement
directory with similar capabilities and print a warning message. Applications
should use this directory for communication and synchronization purposes and
should not place larger files in it, since it might reside in runtime memory and
cannot necessarily be swapped out to disk."

Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple