How to Install and Uninstall lua-resty-lrucache Package on Kali Linux
Last updated: November 26,2024
1. Install "lua-resty-lrucache" package
Here is a brief guide to show you how to install lua-resty-lrucache on Kali Linux
$
sudo apt update
Copied
$
sudo apt install
lua-resty-lrucache
Copied
2. Uninstall "lua-resty-lrucache" package
This tutorial shows how to uninstall lua-resty-lrucache on Kali Linux:
$
sudo apt remove
lua-resty-lrucache
Copied
$
sudo apt autoclean && sudo apt autoremove
Copied
3. Information about the lua-resty-lrucache package on Kali Linux
Package: lua-resty-lrucache
Version: 0.13-10
Installed-Size: 42
Maintainer: Jan Mojžíš
Architecture: all
Provides: lua5.1-resty-lrucache
Depends: libluajit2-5.1-2
Size: 10340
SHA256: 74b1a5621936fa0aac1e85dfe2ee49f8fa9dad1856bdbc52e4109528916a8400
SHA1: b95eb6c9ee326da636796989efb869d4053c821c
MD5sum: d7741f20bc191979dd244b1f2f5fbffd
Description: Simple LRU cache for the ngx_lua module
The LRU cache resides completely in the Lua VM and is subject to Lua GC.
As such, do not expect it to get shared across the OS process boundary.
The upside is that you can cache arbitrary complex Lua values (such as deep
nested Lua tables) without the overhead of serialization (as with ngx_lua's
shared dictionary API). The downside is that your cache is always limited to
the current OS process (i.e. the current Nginx worker process). It does not
really make much sense to use this library in the context of init_by_lua
because the cache will not get shared by any of the worker processes (unless
you just want to "warm up" the cache with predefined items which will
get inherited by the workers via fork()).
Description-md5:
Homepage: https://github.com/openresty/lua-resty-lrucache
Lua-Versions: 5.1
Section: net
Priority: optional
Filename: pool/main/l/lua-resty-lrucache/lua-resty-lrucache_0.13-10_all.deb
Version: 0.13-10
Installed-Size: 42
Maintainer: Jan Mojžíš
Architecture: all
Provides: lua5.1-resty-lrucache
Depends: libluajit2-5.1-2
Size: 10340
SHA256: 74b1a5621936fa0aac1e85dfe2ee49f8fa9dad1856bdbc52e4109528916a8400
SHA1: b95eb6c9ee326da636796989efb869d4053c821c
MD5sum: d7741f20bc191979dd244b1f2f5fbffd
Description: Simple LRU cache for the ngx_lua module
The LRU cache resides completely in the Lua VM and is subject to Lua GC.
As such, do not expect it to get shared across the OS process boundary.
The upside is that you can cache arbitrary complex Lua values (such as deep
nested Lua tables) without the overhead of serialization (as with ngx_lua's
shared dictionary API). The downside is that your cache is always limited to
the current OS process (i.e. the current Nginx worker process). It does not
really make much sense to use this library in the context of init_by_lua
because the cache will not get shared by any of the worker processes (unless
you just want to "warm up" the cache with predefined items which will
get inherited by the workers via fork()).
Description-md5:
Homepage: https://github.com/openresty/lua-resty-lrucache
Lua-Versions: 5.1
Section: net
Priority: optional
Filename: pool/main/l/lua-resty-lrucache/lua-resty-lrucache_0.13-10_all.deb