Oninit® Log Ripper — Binary Rename Release Note

The Ripper's daemon binary and shared library were renamed from oni_logripper to oni_ripper. The change is mechanical — same code, same protocol, same metrics, same operational contract. The new name reads cleaner in operator contexts (status lines, systemd, package managers, command-line invocations) and matches the way customers refer to the product informally.

This page is for operators upgrading from a pre-rename installed package. New installs see the new names from the start and the rename is invisible. Upgrades through RPM / DEB are handled by the package metadata — the package manager removes the old package, installs the new one, and a compat symlink at /usr/bin/oni_logripper points at the new binary so any existing operator scripts continue to resolve.

What changed

What did NOT change

Operationally-visible things deliberately kept under the old name so running deployments don't break:

• Prometheus metric names stay as oni_logripper_* (e.g. oni_logripper_records_total, oni_logripper_lag_seconds). Customer Grafana dashboards keep working without the operator touching them. A future release may add aliases under the new prefix; nothing is removed.
• Service user / group remain oni_logripper:oni_logripper. The home directory, file ownerships, and any sudoers rules referencing the user stay in place.
• Helper script oni_logripper.sh keeps its filename inside /usr/share/oni_ripper/; the script is referenced by name from RPM specs and operator runbooks.
• Wrapper / sysusers / tmpfiles / environment / sysconfig source files keep their old basenames inside the packaging tree. They're internal to the package and referenced by their old paths from the spec; renaming them is purely cosmetic.
• Kafka client_id default stays oni_logripper. Kafka brokers, monitoring, and any consumer-side filtering on client_id continue to work without operator action.
• Public CDC-stream record content — SQL formatting, dialect rewriter behaviour, ALTER emission, the transforms framework, all unchanged. The captured byte stream is byte-for-byte identical across the rename.

Upgrade path

RPM hosts

# The new package Provides + Obsoletes the old one. dnf / yum
# pick up the rename automatically — one command, both halves.
sudo dnf upgrade oni_ripper

Behind the scenes the new RPM declares Provides: oni_logripper and Obsoletes: oni_logripper, so the old package is removed in the same transaction the new one is installed. The post-install scriptlet creates the /usr/bin/oni_logripper compat symlink. The uninstall post-scriptlet removes it.

DEB hosts

sudo apt install ./oni-ripper_1.0.0_amd64.deb

The Debian package's postinst creates the /usr/bin/oni_logripper compat symlink. The package control file declares Replaces: oni-logripper so a side- by-side install is impossible.

From-source builds

A clean make after the rename produces the new artefact names. Operators with custom build wrappers updating /usr/local/bin/oni_logripper directly should add a post-install symlink themselves, mirroring what the RPM / DEB post-install does:

sudo ln -sf /usr/local/bin/oni_ripper /usr/local/bin/oni_logripper

Operator-facing checklist

After the upgrade lands the only things to verify:

• The oni_ripper service is running: systemctl status oni_ripper. The legacy systemctl status oni_logripper alias also returns the same status row, so monitoring scripts that polled the old name keep working.
• The config moved cleanly. The new install reads /etc/oni_ripper/oni_ripper.yml; the package's post-install copies the operator's prior /etc/oni_logripper/oni_logripper.yml into the new location if the new file doesn't already exist. If both files exist (rare — partial prior install) the package keeps the new file and leaves the old one for the operator to remove.
• State files moved. /var/lib/oni_ripper/state/ now carries the LSN checkpoint(s); the package's post-install migrates the operator's prior /var/lib/oni_logripper/state/ contents on first run if the new directory is empty.
• Logs land at the new path: /var/log/oni_ripper/oni_ripper.log. Existing log-rotation rules referencing the old path keep working until they expire the old files; the new files land under the new path on every rotation.
• The Prometheus scrape continues to see the same metric names. Grafana dashboards do not need editing.

Why the rename

"Log Ripper" was the working name during development — it emphasises the byte-level reader pulling records out of the Informix logical log. The customer-facing reading "ripper" became the more natural shorthand once the product had a public surface (release packaging, command-line invocations, documentation pages). The binary now matches that shorthand.

The change is conservative by construction. Anything an operator or downstream system observed under the old name (metric names, service user, helper script filename, Kafka client_id, CDC stream content) was deliberately kept. The symlink and the systemctl alias keep legacy invocations working indefinitely — no rush on the operator's side to update runbooks.