maint: avoid a valgrind memory leak warning from pinky
commit90e0e9bf58fd5c9b6aa86c22c6351d830ed1c6eb
authorPádraig Brady <P@draigBrady.com>
Wed, 10 Jul 2013 00:07:57 +0000 (10 01:07 +0100)
committerPádraig Brady <P@draigBrady.com>
Thu, 11 Jul 2013 23:24:13 +0000 (12 00:24 +0100)
tree3d034cd4df3cd3e51dbc69bd0138bea1aec4877b
parent3ebc58cc4370567be7301e02b661a2fe5478d86c
maint: avoid a valgrind memory leak warning from pinky

Similarly to commit v8.21-84-g8d2da3f in src/uptime.c
avoid a "definitely lost" error from valgrind.  Note this
only happens with pinky when compiled without optimization,
in which case certain paths aren't eliminated casuing
valgrind to trigger the message.  Note also that coverity
flags this "resource leak" too.

* src/pinky.c (short_pinky): free utmp_buf for developer builds.
src/pinky.c