Bug 26055 - Improve CanActivateSessions for OpenSolaris
Summary: Improve CanActivateSessions for OpenSolaris
Status: RESOLVED FIXED
Alias: None
Product: ConsoleKit
Classification: Unclassified
Component: Daemon (show other bugs)
Version: unspecified
Hardware: Other Solaris
: medium major
Assignee: william.jon.mccann
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-14 21:40 UTC by Halton Huo
Modified: 2010-05-19 19:53 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
Enhancement CanActivateSessions for OpenSolaris (2.82 KB, patch)
2010-01-14 22:11 UTC, Halton Huo
Details | Splinter Review
Enhancement CanActivateSessions for OpenSolaris (3.04 KB, patch)
2010-05-18 04:47 UTC, Halton Huo
Details | Splinter Review
Rewrite to avoid lots of ifdef based on Ray's review (3.17 KB, patch)
2010-05-18 21:53 UTC, Halton Huo
Details | Splinter Review

Description Halton Huo 2010-01-14 21:40:31 UTC
VT is always enabled on Linux, on Solaris and OpenSolaris it is not true always.

VT can be on and off by running 
# svcadm enable vtdaemon
# svcadm disable vtdaemon

Now CanActivateSessions return TRUE if the seat is static. I'd say on Solaris, it should also check whether the service vtdaemon is online.
Comment 1 Halton Huo 2010-01-14 22:11:46 UTC
Created attachment 32651 [details] [review]
Enhancement CanActivateSessions for OpenSolaris
Comment 2 Halton Huo 2010-05-18 04:47:16 UTC
Created attachment 35724 [details] [review]
Enhancement CanActivateSessions for OpenSolaris
Comment 3 Halton Huo 2010-05-18 21:53:51 UTC
Created attachment 35746 [details] [review]
Rewrite to avoid lots of ifdef based on Ray's review

Based on Ray's review the patch - http://lists.freedesktop.org/archives/consolekit/2010-May/000086.html - I rework the patch with solution #2.
Comment 4 Ray Strode [halfline] 2010-05-19 08:00:29 UTC
Comment on attachment 35746 [details] [review]
Rewrite to avoid lots of ifdef based on Ray's review

seems fine


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.