pkg.soopen package index

brew / Rang 8395

jlog mit Homebrew installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für jlog in AI-Agent-Workflows.

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install jlog

local Homebrew formula metadata

Überblick

Paketzusammenfassung

Pure C message queue with subscribers and publishers for logs

Befehle und Aliase

  • jlog_change_endian
  • jlog_sanity_check
  • jlogctl
  • jlogtail

Verlauf

Projektgeschichte und Nutzung

JLog is a pure-C durable message queue whose name expands to journaled log. It gives publishers and multiple subscribers a low-level on-disk log abstraction, with segment files retained until subscribers have consumed and checkpointed them.

Projektgeschichte

The project comes from OmniTI Labs and the README lists Wez Furlong, Alec Peterson, George Schlossnagle, Theo Schlossnagle, and Alexey Toptygin as the team. The changelog begins with a 1.0 initial release on 2009-05-13, placing JLog in the older generation of C infrastructure libraries built for reliable log and event pipelines.

JLog evolved through operational fixes and API additions rather than broad feature expansion. The 2.x line added Darwin support, `jlogtail`, repair APIs, Java and PHP support, bulk reads, precommit-buffer performance work, and later filesystem-focused fixes around `mmap`, compression, and short writes.

Adoptionsgeschichte

The README documents installation via FreeBSD's `databases/jlog` port and Homebrew on macOS, while the input package metadata records Homebrew packaging. Its adoption story is narrower than general-purpose queues because it is a library and CLI toolkit for systems that need local durability rather than a networked broker.

Wie es verwendet wird

JLog is used when an application needs to write records locally and let one or more subscribers consume them later. The README's sample scenario is log shipping: server A writes to a JLog if server B is down, so A keeps operating and B can later consume messages.

The concepts document explains the core model: a JLog is a directory containing control files and segment files; writers append messages; subscribers keep unique names and checkpoint progress; segment files are removed after all subscribers have moved past them.

Warum Paket-Nerds sich dafür interessieren

JLog is package-nerdy because it is small, old-school C infrastructure: not a fashionable distributed queue, but a durable local primitive with command-line tools such as `jlogctl` and `jlogtail`. It matters in package indexes as a compact building block for logging and asynchronous notification systems.

Zeitleiste

  • 2009: Version 1.0 is released.
  • 2011: Version 1.2 fixes interrupted `fstat()` handling and an uninitialized variable.
  • 2013: Version 1.2.2 adds PHP and Java JNI support.
  • 2015: Version 2.0.0 adds Darwin support, `jlogtail`, cleanup APIs, and robustness work.
  • 2016: Version 2.2.1 adds a precommit buffer and lockless writes using `pwritev`.
  • 2017: Version 2.3.0 adds the bulk-read API.
  • 2020: Version 2.5.0 reworks `jlogctl` around subcommands and adds repair/metastore reconstruction.
  • 2024: Version 2.6.0 adds an option to switch message reads from `mmap` to `pread` and fixes compression and short-write issues.

Related projects

  • JLog sits near local durable queues, log buffers, and broker-adjacent infrastructure rather than general log viewers. Its README contrasts the low-level local queue with the network service an implementor would build around it for remote consumption.

Quellen

  • Project README, concepts document, changelog, GitHub repository metadata, and Homebrew formula metadata.

Sicherheitslage

Risikostufe: grün

narrow executable package without higher-risk signals.

Risikoklassifikator

grün Risiko · niedrig Konfidenz · appliance

Warum

  • narrow executable package without higher-risk signals

Signale

  • metadata:no-higher-risk-signals

Installationsverhalten

  • Es wurden keine Homebrew-Bottle-Metadaten erfasst.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
jlog_change_endianExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.
jlog_sanity_checkExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.
jlogctlExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.
jlogtailExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-08-03
Manager-Version2.6.0
Manager aktualisiert
lokale Datenunbekannt
Upstreamnicht verfügbar
neueste erkannte Versionnicht erkannt
  • OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:jlog
Version2.6.0
PaketmanagerHomebrew
Homepagehttps://labs.omniti.com/labs/jlog
Repositoryhttps://github.com/omniti-labs/jlog
Bottlenicht erfasst
Dienstkeiner deklariert

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Verwendete Quellen

  • Geiger risk classifier
  • cross-ecosystem install command graph
  • curated package history
  • pkg.so package database
  • pkgdb category and tag curation