Bug 28108

Based on a cron.core image from my favorite, long running internet server
appliance, I discovered (with help from gdb) that cron was leaking memory.

By code inspection, I discovered 2 leaks.

1. Calls were made to login_getclass() without a cooresponding call to
login_close(). This leaks 1 login_cap_t (plus associated data storage) for
every crontab entry. It appears this bug was introduced back in late 1997.

2. There was a possibility of additional leakage (e->class) due to the way
storage was freed in the error case for the call to entry.c:loadentry().

Fix: Apply the patch below.
How-To-Repeat: Fire up cron and keep touching crontab files to ensure it reloads the files
often. Use ps to check on the memory usage or wait long enough for it to
exhaust its memory limit. (While testing, I also put in a syslog() in to
verify it is leaking the login_cap_t once per entry.)