| commit | f6955e5046e0d457ce4e958fa4667800c1046cc8 | |
| author | Ben Kibbey <bjk@luxsci.net> | |
| Wed, 19 Nov 2008 00:02:53 +0000 (18 19:02 -0500) | ||
| committer | Ben Kibbey <bjk@luxsci.net> | |
| Wed, 19 Nov 2008 00:02:53 +0000 (18 19:02 -0500) | ||
| tree | 85477845581458c3b690cad4f222857654c79465 | treesnapshot (tar.gz zip) |
| parent | 2080828ee85d7f711661e67b75c0964d7b11dbf4 | commitdiff |
Revert "Fixed OPEN and SAVE to use the "key_file" if specified. If set
and an"
This reverts commit fad226bde47503b540e4b172fd58b12d234a1e11.
After thinking about this feature, it doesn't really make sense to have
it. If there was a key file specified in the configuration then it is
read on startup and the file is then cached. If for some reason the
cache timer were to expire the cache entry, this feature would allow the
file to be re-cached with no interaction. So it's kinda pointless. Same
goes for commit 3d40712.
So if you have a key_file config entry and it gets removed from the
cache, you'll have to restart pwmd for it to get cached again. This can
be a problem for a remote client. Just be careful what cache commands
you send.
and an"
This reverts commit fad226bde47503b540e4b172fd58b12d234a1e11.
After thinking about this feature, it doesn't really make sense to have
it. If there was a key file specified in the configuration then it is
read on startup and the file is then cached. If for some reason the
cache timer were to expire the cache entry, this feature would allow the
file to be re-cached with no interaction. So it's kinda pointless. Same
goes for commit 3d40712.
So if you have a key_file config entry and it gets removed from the
cache, you'll have to restart pwmd for it to get cached again. This can
be a problem for a remote client. Just be careful what cache commands
you send.
| src/commands.c | diffblobblamehistory | |
| src/common.h | diffblobblamehistory | |
| src/pwmd.c | diffblobblamehistory |