[10:00] <fouga> Hello everyone,I got a Kerberos ticket issue on client side.
[10:00] <fouga> Is someone able to help me please?
[10:01] <fouga> Thanks
[10:13] <effendy[m]> Just ask the question, concretely, if you hope to receive any help.
[10:26] <fouga> After connecting on my session to connect with Kerberos and it failed.
[10:26] <fouga> klist:
[10:26] <fouga> klist: Credentials cache keyring persistant not found
[10:26] <fouga> I have to do kinit each time to make it work.
[10:26] <fouga> Do you have an idea why is happening please ?
[10:26] <fouga> effendy[m]
[10:26] <fouga> and How to fix it ?
[10:27] <effendy[m]> No, I've no idea - I've explained the same thing on matrix :) I'm just telling you how to ask the question, it doesn't mean that I know anything about the topic. But this way you have a better change that someone will help you.
[10:28] <effendy[m]> *chance
[11:43] <DWD> Hey, what is the current advice for adding scripts to /etc/update-motd.d/ to run in the 100-* range?  Globbing causes 100 to be run after 10-* and before 50-*.  I've prefixed with x- for now.  Is it worth setting the default script names to be padded with zeros to preserve the order?
[11:50] <DWD> Found this channel on matrix, so I'll move to that account for convenience :)
[12:02] <frickler> DWD-Daniel[m]: my advice would be: don't. if you have anything that needs to run after a 99-* script, then that script obviously should not carry the "always-run-me-last" tag that 99 semantically is
 "DWD-Daniel: my advice would be..." <- Thanks for challenging the idea, it made me realised my eyes deceived me and that the last script in that directory is 98-*, leaving room for use of  `99-*`. I think that leaves a suitable option of using N=99, with a name of `NN-MM-description` to facilitate ordering. Thanks :)
[21:41] <richd> hi, trying to do updates, and apt is timing out getting to ports.ubuntu.com
[21:42] <richd> working for anyone else?
[21:57] <oerheks> richd,  for what ubuntu version?
[21:58] <sergiodj> richd: can you try again?  it's working here now; I think it was a temporary glitch
[22:31] <richd> sergiodj: all good now.  Thanks