`911d641`

daemon: Remove debug eprintln statements

Remove informational eprintln debug statements that were added during
development. Error messages in session.rs child process are retained
since tracing is not fork-safe and eprintln is the only way to report
errors from the forked child.

Authored by mfwolffe <wolffemf@dukes.jmu.edu> 3 months ago

SHA: 911d6413c5529538089d4ef10898c8764e9db9eb
Parents: c6fbe97
Tree: 1d8c1b5

2 changed files

Status	File	+	-
M	`gardmd/src/main.rs`	0	7
M	`gardmd/src/session.rs`	0	10

gardmd/src/main.rsmodified

              tracing::warn!(error = %e, "Failed to kill greeter");
+         }
 -        eprintln!("[MAIN] Greeter session ended, processing result");
          tracing::debug!(?session_result, "Greeter session ended, processing result");
          match session_result {
              Ok(Some(session_info)) => {
 -                eprintln!("[MAIN] Got session_info: {} {:?} ({})",
 -                    session_info.username, session_info.cmd, session_info.session_type);
                  tracing::info!(
                      "Processing session start: {} {:?} ({})",
                      session_info.username,
          let (response, session_info) = handle_greeter_request(request, &mut auth).await;
 -        eprintln!("[IPC] About to send response, has_session_info={}", session_info.is_some());
          tracing::debug!(?response, has_session_info = session_info.is_some(), "Sending response to greeter");
          conn.send(&response).await?;
 -        eprintln!("[IPC] Response sent successfully");
 -        tracing::debug!("Response sent successfully");
          if let Some(info) = session_info {
 -            eprintln!("[IPC] Returning session info: {} {:?}", info.username, info.cmd);
              tracing::info!(
                  username = %info.username,
                  cmd = ?info.cmd,

gardmd/src/session.rsmodified

+         }
+     }
 -    // Execute the session command
 -    eprintln!("[SESSION] Executing: {} {:?}", cmd_path, cmd_args);
+-
      // execve replaces the process image
      match nix::unistd::execve(&cmd_cstr, &argv, env_vars) {
          Ok(_) => unreachable!(), // execve doesn't return on success
  ) -> Result<()> {
      // Set environment variables BEFORE creating PAM client
      // pam_systemd reads these to determine session type and VT
 -    eprintln!("[PAM] Setting environment for pam_systemd: type={}, vt={}", session_type, vt);
      std::env::set_var("XDG_SESSION_TYPE", session_type);
      std::env::set_var("XDG_VTNR", vt.to_string());
      std::env::set_var("XDG_SEAT", "seat0");
      std::env::set_var("XDG_SESSION_CLASS", "user");
 -    eprintln!("[PAM] Creating PAM client for user {}", username);
+-
      let mut client = Client::with_password(PAM_SERVICE_NAME)
          .map_err(|e| anyhow!("Failed to create PAM client: {:?}", e))?;
      client.conversation_mut().set_credentials(username, password);
 -    eprintln!("[PAM] Authenticating...");
      client
          .authenticate()
          .map_err(|e| anyhow!("PAM authentication failed: {:?}", e))?;
 -    eprintln!("[PAM] Opening session...");
      client
          .open_session()
          .map_err(|e| anyhow!("PAM open_session failed: {:?}", e))?;
 -    eprintln!("[PAM] Session opened successfully");
+-
      // Keep the client alive - don't let it drop and close the session
      // The session will be closed when the process exits
      std::mem::forget(client);