Custom Query (1145 matches)
Results (73 - 75 of 1145)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #459 | duplicate | alpine should respect ATHENA_USER as FROM address | adehnert | |
| Description |
When you run Alpine on a machine where your local user is differently named from your Athena user, Alpine should somehow be configured to send mail from $ATHENA_USER@…, not $USER@…. Unfortunately, this seems mildly difficult, since Alpine doesn't appear to directly provide a way set the user part of the sender (and appears to use /etc/passwd or something, not $USER, to get username information). You can sort of handle this by adding alt-addresses=$ATHENA_USER@… in the pinerc, and by adding a default role that sets the from address to $ATHENA_USER@… (see http://mailman2.u.washington.edu/pipermail/alpine-info/2009-January/001606.html). (This does seem somewhat kludgy, and will cause mail to/from $USER@… to appear to/from you.) |
|||
| #467 | duplicate | Unclean shutdown of reactivate-2 causes time-consuming schroot cleanup | jdreed | |
| Description |
Rebooting an uncleanly shutdown reactivate-2 machine causes it to attempt to recover schroot sessions. Recovery fails because the directory /var/lib/schroot/union/overlay/login-{$uuid} does not exist, but it's still somewhat time consuming to do this on a slower (620, HP) machine. Can we skip this step, since presumably we never care about recovering schroot sessions on cluster machines? |
|||
| #489 | duplicate | Follow up with NIST on getting the KDC upgraded to play nice with stock krb5-1.8 | geofft | jdreed |
| Description |
We can set allow_weak_crypto in the meantime (#488), but we should follow up on this in the general case. |
|||
