summaryrefslogtreecommitdiff
path: root/daemon/gdm-session-worker-job.c
diff options
context:
space:
mode:
authorRay Strode <rstrode@redhat.com>2009-01-16 11:00:08 -0500
committerRay Strode <rstrode@redhat.com>2011-06-13 20:33:47 -0400
commit55a9a413093dbd63082752761b1776626323cab3 (patch)
treedcce8e003b8d29d7dc1082c890194e5baff2bf6f /daemon/gdm-session-worker-job.c
parentdc94d6663666189a41d072dc165a557b36ca01d5 (diff)
downloadgdm-55a9a413093dbd63082752761b1776626323cab3.tar.gz
daemon: Make current pam conversation explicit throughout code
We want to eventually support having multiple simultaneous PAM conversations in one login screen (so, e.g., username/password, smart card, and fingerprint all work at the same time). This commit refactors the session code to be in terms of a conversation object. With this change, it should be easier later to have multiple conversation objects. The conversation is named by the pam service the login screen is talking to.
Diffstat (limited to 'daemon/gdm-session-worker-job.c')
-rw-r--r--daemon/gdm-session-worker-job.c7
1 files changed, 7 insertions, 0 deletions
diff --git a/daemon/gdm-session-worker-job.c b/daemon/gdm-session-worker-job.c
index c13a0a29..caa22d91 100644
--- a/daemon/gdm-session-worker-job.c
+++ b/daemon/gdm-session-worker-job.c
@@ -303,6 +303,13 @@ gdm_session_worker_job_stop (GdmSessionWorkerJob *session_worker_job)
return TRUE;
}
+GPid
+gdm_session_worker_job_get_pid (GdmSessionWorkerJob *session_worker_job)
+{
+ g_return_val_if_fail (GDM_IS_SESSION_WORKER_JOB (session_worker_job), 0);
+ return session_worker_job->priv->pid;
+}
+
void
gdm_session_worker_job_set_server_address (GdmSessionWorkerJob *session_worker_job,
const char *address)