On 11/09/2015 02:33, Daniel Reurich wrote:
On 10/09/15 23:46, Roger Leigh wrote:
On 10/09/2015 12:11, tilt! wrote:
Since i already use $HOME/.config for configuration data,
which more precisely is the default setting of XDG_CONFIG_HOME
(according to [1]), i would like to consider the pendant
Hi,
On 09/17/2015 10:12 AM, Roger Leigh wrote:
> On 11/09/2015 02:33, Daniel Reurich wrote:
>> We could either use $USER_$SESSIONID or $USER/$SESSIONID to implement
>> multiple sessions per user.
>
> This is definitely possible. It would probably need some thought on
> how to determine which
On Thu, Sep 17, 2015 at 11:23:10AM +0200, Jaromil wrote:
> > If rundirs are on non-volatile storage, my implementation can delete
> > them at system shutdown (assuming an orderly shutdown is performed).
>
> if you use the /tmp prefix as default then you don't even need to handle
> such a deletion
On 17/09/2015 10:01, tilt! wrote:
Hi,
On 09/17/2015 10:12 AM, Roger Leigh wrote:
> On 11/09/2015 02:33, Daniel Reurich wrote:
>> We could either use $USER_$SESSIONID or $USER/$SESSIONID to implement
>> multiple sessions per user.
>
> This is definitely possible. It would probably need
On 17/09/15 21:01, tilt! wrote:
Hi,
On 09/17/2015 10:12 AM, Roger Leigh wrote:
> On 11/09/2015 02:33, Daniel Reurich wrote:
>> We could either use $USER_$SESSIONID or $USER/$SESSIONID to implement
>> multiple sessions per user.
>
> This is definitely possible. It would probably need some
On 17/09/2015 10:31, Tomasz Torcz wrote:
On Thu, Sep 17, 2015 at 11:23:10AM +0200, Jaromil wrote:
If rundirs are on non-volatile storage, my implementation can delete
them at system shutdown (assuming an orderly shutdown is performed).
if you use the /tmp prefix as default then you don't even
On Thu, 17 Sep 2015, tilt! wrote:
> FYI, i am working on an implementation of XDG_RUNTIME_DIR at [1]
> that can be configured to whatever a site-maintainer finds suitable.
cheers! good effort
> The default rundir prefix i am using is "/run/xdg-runtime"
but then again, considering Roger's
On 17/09/2015 12:29, Daniel Reurich wrote:
On 17/09/15 21:01, tilt! wrote:
Hi,
On 09/17/2015 10:12 AM, Roger Leigh wrote:
> On 11/09/2015 02:33, Daniel Reurich wrote:
>> We could either use $USER_$SESSIONID or $USER/$SESSIONID to implement
>> multiple sessions per user.
>
> This is
On Thu, Sep 17, 2015 at 11:29:50PM +1200, Daniel Reurich wrote:
> I think XDG_SESSION_COOKIE is more aimed at restoring the previously
> saved session state on login, ie start up all the applications and
> get them to exactly the same state as it was at when previous
> log-out occured (assuming
Hi Daniel,
On 09/17/2015 01:29 PM, Daniel Reurich wrote:
> [...]
>> The implementation so far manages to do without any form of PAM
>> module or login-managing daemon process. It's my intention to
>> keep it that way.
>
> That's great, but don't create something that would rule out PAM
> or
On 09/13/2015 03:13 AM, Isaac Dunham wrote:
[...]
>
> One detail I'm not sure if you implemented: I suggested that default
> be to create .../$UID if needed, but you can pass "-n" to create a
> new session.
The software provides config files and a script in /etc that could
be modified to
It maybe helps that i now changed project visibility from "private" to
"public" *sighs*
This has been corrected - Share and enjoy!
On 09/13/2015 03:13 AM, Isaac Dunham wrote:
On Sat, Sep 12, 2015 at 10:32:13PM +0200, tilt! wrote:
https://git.devuan.org/tilt/xdg-compat
git.devuan.org[0:
Hi,
On 09/12/2015 12:52 PM, tilt! wrote:
> [...]
> I will think about this a bit more, but currently it converges
> towards a SUID helper and a separately configured directory for
> refcounts.
Here's my shot at it:
https://git.devuan.org/tilt/xdg-compat
It uses a setuid-bit-executable that
On Sat, Sep 12, 2015 at 10:32:13PM +0200, tilt! wrote:
> Hi,
>
> On 09/12/2015 12:52 PM, tilt! wrote:
> > [...]
> > I will think about this a bit more, but currently it converges
> > towards a SUID helper and a separately configured directory for
> > refcounts.
>
> Here's my shot at it:
>
>
Hi Isaac,
On 09/11/2015 09:30 PM, Isaac Dunham wrote:
> On Fri, Sep 11, 2015 at 11:23:38AM +0200, tilt! wrote:
Unadressed remains the lifecycle of $XDG_RUNTIME_DIR,
>> specifically: [...]
>> * When is $XDG_RUNTIME_DIR created?
>> [...]
Currently my best guess is that this should be
On 09/11/2015 03:33 AM, Daniel Reurich wrote:
> [...]
> We could either use $USER_$SESSIONID or $USER/$SESSIONID to
> implement multiple sessions per user.
> [...]
Hi Daniel,
what is $SESSIONID? How is the value determined?
Kind regards,
T.
___
Dng
On 09/11/2015 07:33 AM, tilt! wrote:
> [...]
> #1 A "prefix" for XDG_RUNTIME_DIR, meaning the directory where
> runtime directories are created; [...]
>
>XDG_RUNTIME_PREFIX="/tmp/xdg-runtime/user"
>
> This definition could go to "/etc/xdg/runtime-prefix.default"
>
> #2 A procedure that, if
On Thu, 10 Sep 2015, Roger Leigh wrote:
> So my recommendation here would be to
> - place /run/user in a subdirectory of /tmp
> - configure XDG_RUNTIME_DIR to use this location either in a PAM
> module, or even by hardcoding the default to use this location--the
> specification might not provide
Hi,
for jack-autostart i need to store some data in a per-user file
across the lifetime of the jackd process. It's a pretty typical
tempfile, when the process goes away, it will be considered stale,
when the system is rebooted, it should be discarded. It may exist
once per user.
Since i already
On 10/09/2015 12:11, tilt! wrote:
Since i already use $HOME/.config for configuration data,
which more precisely is the default setting of XDG_CONFIG_HOME
(according to [1]), i would like to consider the pendant
XDG_RUNTIME_DIR for the tempfile i have described.
Unfortunately, the
On 10/09/15 23:46, Roger Leigh wrote:
On 10/09/2015 12:11, tilt! wrote:
Since i already use $HOME/.config for configuration data,
which more precisely is the default setting of XDG_CONFIG_HOME
(according to [1]), i would like to consider the pendant
XDG_RUNTIME_DIR for the tempfile i have
Hi,
On 09/10/2015 10:01 PM, Roger Leigh wrote:
> On 10/09/2015 20:33, tilt! wrote:
>> [...]
>> Come to think of it, my choice of
>>
>> ${XDG_RUNTIME_DIR:-/tmp/run/$USER}
>>
>> is no good, because, just as an example, if $USER comes from an AD
>> domain or LDAP it might contain '\'; in the least,
On 10/09/2015 20:33, tilt! wrote:
Hi,
in Ubuntu defaults are in X11/Xsession.d/60x11-common_xdg_path
which is shipped by x11-common and sourced by XSession
>
BTW there is some XDG_* env setting also in X11/Xsession.d/00upstart
Ok, now if only we knew what to actually use as a default for
23 matches
Mail list logo
