Re: [systemd-devel] Two questions about logind and seats
On Tuesday, August 1, 2017 3:00:25 AM EDT Lennart Poettering wrote: > On Mo, 31.07.17 21:24, nerdopolis (bluescreen_aven...@verizon.net) wrote: > > > > > First, when I attach a 2nd graphics card to seat1, it seems > > > > CanMultisession is > > > > set to 0. Is there a way to change that? or is that only supported on > > > > seat0, > > > > that supports the TTYs? > > > > > > Yes, this is only supported where VTs are supported, and that is > > > only seat0. > > > > Thanks, It's currently a kernel limitation I assume? I guess I'll worry > > about > > multiple sessions on non seat0 seats when it _is_ supported. > > Yeah the VCs are drawn by the kernel, hence doing multi-session on > other but the first seat would mean either updating the kernel or > doing something purely in userspace with a userspace terminal > renderer. David Hermann was working on something like this, but he > lost interest. > > Lennart > > Out of curiosity, what would the likes of Weston, X, and other Display Servers need on seats outside of seat0? A device to set KD_GRAPHICS on, like a special type of pty or something? ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd-234 automount fails
Without the x-systemd.automount option just "mount /mnt/data" works fine after reboot. Regards, Vlad. On 31/07/17 16:36, Lennart Poettering wrote: > On Do, 27.07.17 12:27, Vlad (vo...@vovan.nl) wrote: > >> Hello, >> >> Autogenerated from fstab mount unit fails, the relevant fstab entry: >> UUID=xx /mnt/data btrfs >> noatime,autodefrag,discard,subvol=data,nofail,noauto,x-systemd.automount >> >> 0 0 >> >> >From log >> Jul 27 12:09:15 xxx systemd[1]: mnt-data.automount: Got automount >> request for /mnt/data, triggered by 2045 (ls) >> Jul 27 12:09:15 xxx systemd[1]: Mounting /mnt/data... >> Jul 27 12:09:15 xxx systemd[1]: mnt-data.mount: Mount process exited, >> code=exited status=32 >> Jul 27 12:09:15 xxx systemd[1]: Failed to mount /mnt/data. >> Jul 27 12:09:15 xxx systemd[1]: mnt-data.mount: Unit entered failed state. >> >> >> Works fine with systemd versions < 234. > > Hmm, /bin/mount returns 32, which means "mount failure" according to > its documentation... > > If you issue "mount UUID= /mnt/data > btrfsnoatime,autodefrag,discard,subvol=data,nofail,noauto," on the > shell, does it work then? > > Lennart > ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
