I'm hoping all of those MUST items are the responsibility of the OS and not the application using that directory. Am I correct in understanding that $XDG_RUNTIME_DIR is the user-specific directory, so all I need to do is place the socket file there?
Rick On Wed, Nov 28, 2018 at 1:20 PM Moritz Hoffmann <antig...@gmail.com> wrote: > Further down it specifies that "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." I would argue that as long as the daemon is > running in the background the user is not fully logged out. At least this > is how screen and tmux handle it. > > Moritz > > On Wed, Nov 28, 2018, 18:36 Erich Steinböck <erich.steinbo...@gmail.com> > wrote: > >> Should compile without error with latest commit. >> There's still a link error that needs to be resolved. I checked the >> rexxapi libray definition in CMakeLists.txt, but couldn't figure out what's >> wrong. >> ~~~ >> bin/librexxapi.so.5.0.0: undefined reference to >> `SysServerLocalSocketConnectionManager::userServiceName' >> ~~~ >> >> >> >>> https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html >>> >> says:"$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. " >> >> Would that (see bold) mean that we couldn't keep a Rexx script running in >> the background while logging out, because this would remove the socket? >> _______________________________________________ >> Oorexx-devel mailing list >> Oorexx-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >> > _______________________________________________ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel >
_______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel