{"id":16896121,"url":"https://github.com/vcaputo/jio","last_synced_at":"2026-05-09T16:55:56.757Z","repository":{"id":91235872,"uuid":"330656352","full_name":"vcaputo/jio","owner":"vcaputo","description":"jio is an experimental PoC tool for operating on systemd-journald journal files in a continuation passing style in C using io_uring.  Mirror of git://git.pengaru.com/jio","archived":false,"fork":false,"pushed_at":"2021-10-11T01:55:11.000Z","size":166,"stargazers_count":1,"open_issues_count":0,"forks_count":0,"subscribers_count":2,"default_branch":"master","last_synced_at":"2025-03-20T10:24:42.966Z","etag":null,"topics":["async-io","io-uring","systemd-journald"],"latest_commit_sha":null,"homepage":"","language":"C","has_issues":false,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"gpl-3.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/vcaputo.png","metadata":{"files":{"readme":"README","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2021-01-18T12:16:56.000Z","updated_at":"2023-11-17T06:59:34.000Z","dependencies_parsed_at":null,"dependency_job_id":"54d6353b-9c90-4b26-b916-e8a77fa5bdbe","html_url":"https://github.com/vcaputo/jio","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/vcaputo/jio","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/vcaputo%2Fjio","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/vcaputo%2Fjio/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/vcaputo%2Fjio/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/vcaputo%2Fjio/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/vcaputo","download_url":"https://codeload.github.com/vcaputo/jio/tar.gz/refs/heads/master","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/vcaputo%2Fjio/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":276064398,"owners_count":25579006,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","status":"online","status_checked_at":"2025-09-20T02:00:10.207Z","response_time":63,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["async-io","io-uring","systemd-journald"],"created_at":"2024-10-13T17:28:10.095Z","updated_at":"2025-09-20T08:16:37.042Z","avatar_url":"https://github.com/vcaputo.png","language":"C","funding_links":[],"categories":[],"sub_categories":[],"readme":"## Overview\n\n jio is an experimental systemd-journald journal file tool\n \n It deliberately avoids using systemd's sd-journal interface, instead\n directly interfacing with journal files as defined by:\n\n https://github.com/systemd/systemd/blob/v246/docs/JOURNAL_FILE_FORMAT.md\n\n This is an unfinished work-in-progress, use at your own risk, backup your\n journals before using.\n\n\n## Author, License, and Contributing\n\n jio is written by Vito Caputo \u003cvcaputo@pengaru.com\u003e.\n \n jio is licensed under the terms of the General Public License v3.\n\n jio patches are welcome, just email them to \u003cvcaputo@pengaru.com\u003e.\n\n Discussion of systemd-journald or the underlying journal file format\n should occur on the systemd-devel mailing list.  Spare the systemd-devel\n list of discussion specifically about jio patches, bugs, code, or\n programming style, stuff that doesn't relate to systemd-journald or\n journal-file at all should be sent directly to the jio author.\n\n\n## Requirements\n\n jio utilizes the new \"io_uring\" Linux kernel interface, technically\n introduced in v5.1, but v5.9+ is recommended for io_uring.  It's enabled\n in the kernel config with CONFIG_IO_URING=Y, easily confirmed by checking\n /proc/config.gz if present.\n\n The liburing library is used for accessing the low-level io_uring syscalls\n and preparing the associated queue entries.  You can find the source at:\n\n https://git.kernel.dk/cgit/liburing\n\n Otherwise jio is a relatively boring C program using autotools for its\n build system.\n\n\n## Building\n\n To build jio from source, first ensure you've cloned the git repository\n recursively, including submodules:\n \n `git clone --recursive git://git.pengaru.com/jio`\n \n Also ensure you have a working C compiler, liburing, and autotools\n available on the build host.\n \n Bootstrap the build system from the jio source dir:\n \n `./bootstrap`\n \n Then configure and make from a build subdirectory:\n \n `mkdir build \u0026\u0026 cd build \u0026\u0026 ../configure \u0026\u0026 make`\n \n Assuming all goes well, you should have a jio executable at\n \"build/src/jio\".\n\n jio may be run as a regular user without elevated privileges, provided the\n journal files of interest are accessible, like user journal files.  To\n access system journal files generally requires elevated privileges.\n\n\n## Usage\n\n Simply running `jio` with no arguments will print a terse summary of\n key subcommands, e.g.:\n\n ```\n $ src/jio\n Usage: build/src/jio {help,reclaim,report} [subcommand-args]\n $\n ```\n\n This document is unlikely to be kept up to date as available subcommands\n evolve, so it's best to just run jio without any arguments to see what's\n possible.  `jio help` may also show additional subcommands.\n\n At this time, the report subcommand features should be considered safe,\n and if you run it as your regular user it will be limited to only journals\n your user has access to.  If you run it as root, it will open all\n available journals.\n\n The reclaim subcommand is a journal-modifying command, so it should be\n treated with caution especially considering the experimental nature of\n jio.\n\n Generally speaking, make backup copies of your journals before using jio\n in any of its journal-modifying modes, only disposing of them after you've\n verified the results are desirable.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fvcaputo%2Fjio","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fvcaputo%2Fjio","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fvcaputo%2Fjio/lists"}