GitLab

Renewal of kerberos tickets is useful even if no AFS is present.

Obvious example is aiadm-homeless.

In reality the aklog call could be completly removed since -t to kstart does this.

Note it is not considered fatal to kstart if aklog is missing.

After this change:

ls /usr/bin/aklog
ls: cannot access '/usr/bin/aklog': No such file or directory

but we still have

systemctl --user status   aklog.service
● aklog.service
   Loaded: loaded (/home/straylen/.config/systemd/user/aklog.service; enabled; vendor preset: enabled)
  Drop-In: /etc/systemd/user/aklog.service.d
           └─kdestroy.conf
   Active: active (running) since Thu 2022-06-30 10:22:50 CEST; 2min 36s ago
  Process: 3303634 ExecStartPre=/usr/bin/aklog (code=exited, status=0/SUCCESS)
 Main PID: 3303636 (krenew)
   CGroup: /user.slice/user-16568.slice/user@16568.service/aklog.service
           └─3303636 /usr/bin/krenew -K 30 -i -v -L -t

So weird how it has process id and status=0/SUCCESS for it but does.

The downside of this is of course if aklog was present but failing for some reason this would not be noticed....

In addition I have added the -a flag. From the man page:

When run with either the -K flag or a command, always renew tickets each time krenew wakes up. Without this option, krenew will only try to renew a ticket as often as necessary to prevent the ticket from expiring. With this option, krenew will renew tickets according to the interval specified with the -K flag.

This behavior probably should have been the default behavior of -K. The default was not changed to avoid changes for existing users, but for new applications, consider always using -a with -K.

Extra commits:

• Create a pid file and use it.
• Cut release 1.2