$ ck-list-sessions Session4: unix-user = '120' realname = 'RabbitMQ messaging server' seat = 'Seat1' session-type = '' active = FALSE x11-display = '' x11-display-device = '' display-device = '/dev/???' remote-host-name = '' is-local = TRUE on-since = '2012-01-06T17:27:13.153273Z' login-session-id = '' Session5: unix-user = '1000' realname = 'Forest' seat = 'Seat1' session-type = '' active = TRUE x11-display = ':0' x11-display-device = '/dev/tty7' display-device = '' remote-host-name = '' is-local = TRUE on-since = '2012-01-06T17:27:51.421367Z' login-session-id = ''
Interesting. So is this rabbitmq's fault for creating a console session, or lightdm's or consolekit's fault for treating it like a user session?
$ ck-list-sessions
session- type = ''
x11-display- device = ''
display- device = '/dev/???'
remote- host-name = '' 06T17:27: 13.153273Z'
login- session- id = ''
session- type = ''
x11-display- device = '/dev/tty7'
display- device = ''
remote- host-name = '' 06T17:27: 51.421367Z'
login- session- id = ''
Session4:
unix-user = '120'
realname = 'RabbitMQ messaging server'
seat = 'Seat1'
active = FALSE
x11-display = ''
is-local = TRUE
on-since = '2012-01-
Session5:
unix-user = '1000'
realname = 'Forest'
seat = 'Seat1'
active = TRUE
x11-display = ':0'
is-local = TRUE
on-since = '2012-01-
Interesting. So is this rabbitmq's fault for creating a console session, or lightdm's or consolekit's fault for treating it like a user session?