On Fri, 2016-12-02 at 12:28 +, Simon McVittie wrote:
> Does this mean your user is trying to be physically present in two
> places
> at the same time? How is this a useful thing to do? :-)
I thought the same when I came across this requirement. People
explained me that the admins who are
On Fri, 02 Dec 2016 at 13:58:01 +0530, Mohan R wrote:
> Let say if a user already have a session(session0) in a seat (customseat0) and
> he want to start another session in another seat (customseat1).
Does this mean your user is trying to be physically present in two places
at the same time? How
On 12/02/2016 12:28 PM, Simon McVittie wrote:
Does this mean your user is trying to be physically present in two places
at the same time? How is this a useful thing to do?:-)
Clones are very useful things to have.
You just sit a drink a pina colada in hut in bora bora while they do all
the
Kai Krakow [2016-12-02 8:47 +0100]:
> Am Thu, 17 Nov 2016 18:53:53 +0100
> schrieb Lennart Poettering :
> > I now added a small extension to this line: "(to the level the
> > firmware permits this)" ot clarify that we are bound by firmware
> > limitations for this.
> I
Hi,
I'm working on a display-manager for a multiseat environment. Here is how
we use logind
1. create new seat through udev
2. we set the XDG_SEAT in pamenv before calling pam_open_session()
3. we take XDG_SESSION_ID, XDG_RUNTIME_DIR and DBUS_SESSION_BUS_ADDRESS
from pam_systemd
Let say if a
On Fri, Dec 2, 2016 at 10:28 AM, Mohan R wrote:
> Hi,
>
> I'm working on a display-manager for a multiseat environment. Here is how
> we use logind
>
> 1. create new seat through udev
> 2. we set the XDG_SEAT in pamenv before calling pam_open_session()
> 3. we take
Hey accelerometer lovers,
I have, bar any bugs obviously, finished adding support for "mount-
matrix" in iio-sensor-proxy.
The code reads the "ACCEL_MOUNT_MATRIX" udev property of the device,
which it will apply to raw readings. After testing, I will provide a
patch to systemd's hwdb to gather
During coredump generation I could find a temporary uncompressed file
getting generated from the corefile and written to the harddisk, later this
file is getting compressed (if compression was enabled) and then the file
coredump file is stored and this temporary file is removed.
I have a process