| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Mapping between device path and (major, minor).
"/dev/vt" -- (15,*)
"/dev/pts" -- (24,*)
"/dev/console" -- (0,0)
"NO_TTY_VALUE" - (-1,-1)
Also, solaris VT device is named like this.
/dev/console --- VT #1
/dev/vt/2 --- VT #2
/dev/vt/3 --- VT #3
/dev/vt/N --- VT #4
|
|
|
|
|
|
| |
This patch fixes ConsoleKit
so it sets x11-display-device to "/dev/console" when not using
VT.
|
| |
|
|
|
|
|
|
|
|
|
| |
This fixes the Active device so it is set to "/dev/console" when not
using VT. Without this patch, the syslog reports messages like:
Active device: /dev/vt/3508388860
Which is obviously wrong if not using VT at all.
|
|
|
|
|
|
| |
This fixes the patch that
Simon Zhang sent you earlier so that it builds on machines
without VT.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Here's a patch for ConsoleKit to improve supporting Solaris VT. Two
changes are made.
- Solaris supports synchronous event notification in STREAMS. Using
this, we can avoid creating many threads for idle VTs.
By setting the S_MSG flag in an I_SETSIG STREAMS ioctl, applications can
get a synchronous notification of VT switching. In other words, these
processes are able to receive a SIGPOLL signal when a VT switching
succeeds.
- Change a little command line of getting maximum vt console numbers.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Da bus no likey nulls for object paths. Return false and set
error if there is no active session.
|
|
|
|
| |
Also make criticals fatal when starting with --debug.
|
|
|
|
|
| |
Deny first and then allow. Add a simple test
script to check method access policy.
|
|
|
|
| |
This tool opens a session with ConsoleKit and runs a command in it.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This should probably be used by init instead of
logging the event from CK.
|
| |
|
| |
|
| |
|
|
|
|
| |
PAM module
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Also enable reporting this information with ck-history.
|
| |
|
|
|
|
| |
https://bugs.freedesktop.org/show_bug.cgi?id=14175
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch makes polkit an optional dependency. If present
it builds with it. If not, polkit support is disabled.
This patch also adds a --enable-rbac-shutdown=<key> option.
If set, then ConsoleKit will allow shutdown/reboot if the
user has the RBAC key authorization defined. For example,
since the GDM GUI program runs as the "gdm" user, setting
the key for the "gdm" user allows the login program to
shutdown and reboot via ConsoleKit.
Also this patch modifies the tools/solaris/ck-system-restart
and tools/solaris/ck-system-stop scripts to call "/sbin/init 6"
and "/sbin/init 5", which are the right commands for Solaris.
|
|
|
|
|
|
|
|
|
|
| |
Fixes two bugs I found in the code. The first is that
we need some NULL protection around the g_strdup_printf
where we build CK_SESSION_X11_DISPLAY to avoid a crash.
Second, I noticed a bug in the ck_unix_pid_get_hash
function where we weren't parsing the data right and
causing the hash to not get set properly.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Add Stop and Restart methods to the Manager object. We'll rename the
Manager object to System in the near future. Use libpolkit to
determine authorization.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
ConsoleKit tries to find a valid fd it can issue
VT_WAITACTIVE against by iterating across a file list and issuing
ioctl(fd, KDGKBTYPE, &arg), then checking the return value. Not all console
devices support this ioctl, so in some cases it never finds a valid file
descriptor to use, and from then on never marks any session active.
We probably ought to be using something like VT_GETSTATE instead of a keyboard
ioctl, but that's not sufficient to fix it. One fix that seems to work, though
I'm not completely sure if it's the best answer, is to add /dev/tty0 to the list
of files to try before /dev/console.
|
|
|
|
|
|
|
| |
given that my first patch get's applied, it makes sense to remove the
old sysv init script, as it's not really needed anymore. Besides, most
distros will not use this init script anyways as they have special
policies for their init script and provide their own.
|