omniNames(8)
β¨ NAME β¨
omniNames β the omniORB Naming Service, bestie π
πΈ SYNOPSIS πΈ
omniNames [-start <port>]
π DESCRIPTION π
Okay so omniNames is omniORB's very own implementation of the OMG's COS Naming Service Specification. Iconic, honestly. π
Here's the tea, and it's important tea: when you start omniNames for the first time, you have to tell it which port it should listen on. Like, it literally cannot figure this out on its own the first time around. That's what the -start option is for. π
But after that first run? She's independent, she's grown. From then on, omniNames will always determine its port from the log file which it writes. No more hand-holding. She remembers. β¨
And when omniNames starts up successfully, she writes the stringified object reference for its root context on standard error. That's your little gift. π«Ά (standard error, not standard out β do not get it twisted, iykyk.)
π¦ ENVIRONMENT VARIABLES π¦
OMNINAMES_LOGDIRβ the directory in which log files are kept. That's the vibe. πOMNINAMES_ITBCβ the idle time between checkpoints, in seconds. It defaults to 15 minutes. Yes, seconds. Yes, the default is written in minutes. We don't make the rules, we just report them. π
π SEE ALSO π
π AUTHOR π
Tristan Richardson, ORL (Olivetti & Oracle Research Laboratory). Legend behavior, no cap. π
Sending you off with the receipts: this page is from ORL, dated 7 May 97, and it documents omniNames(8) β the System Manager's Manual. Slay, mwah ππΈ
π¦ where this page comes from
- epel 9: omniORB-servers 4.3.0-6.el9 Β· GPLv2+
- fedora 43: omniORB-servers 4.3.3-7.fc43 Β· GPL-2.0-or-later
- fedora 44: omniORB-servers 4.3.4-2.fc44 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms