BSD Portsdevel/liblognorm 2.0.6 DragonFly
Log normalizer
- System
- DragonFly
- Repository
- DPorts
- Maintainer
- [email protected] (as in FreeBSD)
- License
- APACHE20, LGPL21+
- Categories
- devel, net, security
- Package size
- 122.7 KiB, 466.2 KiB installed
Description
liblognorm shall help to make sense out of syslog data, or, actually, any event data that is present in text form.
In short words, one will be able to throw arbitrary log message to liblognorm, one at a time, and for each message it will output well-defined name-value pairs and a set of tags describing the message.
In the other systems
The newest version among them is 2.1.1, as upstream numbers it.
| System | Port | Version | Vulnerabilities | Status | Maintainer | Last update |
|---|---|---|---|---|---|---|
| DragonFly | devel/liblognorm | 2.0.6 behind since 2026-09-20 | none known | - | [email protected] | - |
| FreeBSD | devel/liblognorm | 2.1.1 newest | none known | - | [email protected] | 2026-09-20 |
| OpenBSD | devel/liblognorm | 2.0.9 behind since 2026-09-20 | no data | - | The OpenBSD ports mailing-list <[email protected]> | - |
| NetBSD | sysutils/liblognorm by name | 2.0.6 behind since 2026-09-20 | none known | - | [email protected] | - |
| HardenedBSD | devel/liblognorm | 2.1.1 newest | no data | - | [email protected] | - |
| GhostBSD | devel/liblognorm | 2.1.1 newest | no data | - | [email protected] | - |
Install
Binary package:
pkg install liblognormFrom DPorts:
cd /usr/dports/devel/liblognorm && make install cleanDependency graph
Ports that need it on the left, what it needs to run on the right; at most 8 of each. "Dependencies" below lists them all.
Dependencies
Run dependencies 2
No port depends on this one.
Configuration
No options to configure.
- Service scripts
- none
Message after installing
The previous version of liblognorm (0.3.7) used the libee CEE support library in its API. In 2013, Pavel Levshin converted liblognorm to native JSON, which helped improve performance and simplicity for many client applications. Unfortunately, this change broke interface compatibility (and there was no way to avoid that, obviously...). The current library is the result of that effort. Application developers are encouraged to switch to this version, as it provides the benefit of a simpler API. PREVIOUS VERSIONS ARE INCOMPATIBLE WITH THIS ONE.