Sometimes the gpg script when run inside an improperly configured
authorMarc Fiuczynski <mef@cs.princeton.edu>
Fri, 29 Aug 2008 14:23:02 +0000 (14:23 +0000)
committerMarc Fiuczynski <mef@cs.princeton.edu>
Fri, 29 Aug 2008 14:23:02 +0000 (14:23 +0000)
commitf2c0fc1a912ffcfb759c9d423aa21d1eadc99eef
tree93ddeff13465922b210c0db3a7866bdde3e193c6
parentc4664d5cce7baa030ebaa2fd5a9e71f7072d65ae
Sometimes the gpg script when run inside an improperly configured
vserver (i.e., one where mknod fails.).  Two improvements to the
script:

- remove zero length *.gpg files, as those are turds left over from a
  failed gpg command.

- add in a "check" after the mknod command to have the script fail
  more gracefully.
plc.d/gpg