Custom Query (1145 matches)

Reported by geofft, 15 years ago.

Although we should deal with renumbering mit or whatever we choose to do (see #299) eventually, that's not going to happen soon. In the meantime, it's kind of useless to keep syslogging

Sep  1 13:54:24 tyger hal-acl-tool: nss_nonlocal: removing local group 101 (libuuid) from non-local user geofft 
Sep  1 13:54:24 tyger last message repeated 4 times
Sep  1 13:54:24 tyger getent: nss_nonlocal: removing local group 101 (libuuid) from non-local user geofft 
Sep  1 13:54:24 tyger hal-acl-tool: nss_nonlocal: removing local group 101 (libuuid) from non-local user geofft 
Sep  1 13:54:26 tyger last message repeated 62 times

etc. since that message doesn't help anyone: users don't care, and the Debathena team isn't taking any additional action because that message continues to appear on everyone's system.

I see three mostly-reasonable courses of action:

1. Special-case libuuid/mit in the logging function
2. Suppress this error entirely -- have we seen it be useful for debugging?
3. Don't print the error more than once per session (although "session" probably poorly defined for an NSS module)

Reported by jhamrick, 15 years ago.

If your local password and athena passwords are the same, you don't get tickets on login. This is because in /etc/pam.d/common-auth, first it checks the entered password against the local password, and then only if that fails, does it run pam_krb5.

# here are the per-package modules (the "Primary" block)
auth	[success=2 default=ignore]	pam_unix.so nullok_secure
auth	[success=1 default=ignore]	pam_krb5.so minimum_uid=1 use_first_pass

Running debathena-login on Ubuntu 9.04.

Reported by broder, 15 years ago.

It would be cool to add tab completion to athinfo.

You could use the _known_hosts function for completing the hostname, and then the output of athinfo <hostname> queries for completing the query.

This does have some small challenges. It's possible that the remote host is down, in which case athinfo will hang for some time before timing out; you don't want that hang to hang tab completion as well.

Since all queries (including 'query') are admin-configurable, you can never assume that the output is actually in the right format, or free of undesirable spaces/semicolons/etc.

And you can also never assume that athinfo won't hang after connecting while it's in the process of printing out the query.

To solve the latter two issues, you want to make sure that you kill athinfo after a timeout (probably no more than a second). I'm not sure whether this can be done from pure bash, so you might need a helper script.