LOMIRI-LOCATION-SERVICE(2)

📦 version 3.4.1, in debian trixie, ubuntu questing, ubuntu resolute, ubuntu stonking

💖 LOMIRI-LOCATION-SERVICE 💖

section 2, from the lomiri manual, and yes bestie we're doing the whole thing 🎀

✨ NAME ✨

lomiri-location-service — a location service that aggregates position/velocity/heading updates and exports them over dbus. 💅

🌸 SYNOPSIS 🌸

lomiri-location-service --bus well known bus name --provider provider
[--provider provider] [provider specific options]

🦋 DESCRIPTION 🦋

okay so, no cap: this is a location service that aggregates position/velocity/heading updates and exports them over dbus. that's the whole vibe. it's giving "middleware but make it coordinates." 📍✨

👑 OPTIONS 👑

🫶 these ones control which bus the service is exposed upon and which providers are instantiated

  • --bus=bus — tell the service which bus it should be exposed upon, bestie. the valid values are "session" or "system". pick one, you can't have both. 🙈
  • --provider=provider — say which provider should be instantiated and configured for this service instance. valid values are: geoclue::Provider, gps::Provider and skyhook::Provider. literally those three, periodt. 💅

🧚 these ones control the behavior of the geoclue provider

  • --geoclue::Provider::name=name — the name of the provider on the bus. iconic little name tag situation. 🏷️
  • --geoclue::Provider::path=path — the object path of the provider on the bus. ✨

🌈 these ones control the behavior of the Skyhook provider

  • --skyhook::Provider::username=username — username for authenticating with the Skyhook service. 🔐
  • --skyhook::Provider::realm=realm — realm for authenticating with the Skyhook service. 🗝️
  • --skyhook::Provider::period=period — delay between updates, in [ms]. so like, the gap between glow-ups. ⏱️

💜 these ones control the logging behavior of the service

  • --logtostderr=<boolean, default: false> — log messages to stderr instead of logfiles. defaults to false, so if you want it, you gotta ask for it. 🙈
  • --stderrthreshold=<threshold, default: 2> — copy log messages at or above this level to stderr in addition to logfiles. the numbers of severity levels INFO, WARNING, ERROR, and FATAL are 0, 1, 2, and 3, respectively. Defa
  • --minloglevel=<level, default: 0> — log messages at or above this level. again, the numbers of severity levels INFO, WARNING, ERROR, and FATAL are 0, 1, 2, and 3, respectively. 📊
  • --log_dir=<path, default: ""> — if specified, logfiles are written into this directory instead of the default logging directory. so like, put your diary somewhere else. 🗂️
  • --v=<level, default: 0> — show all VLOG(m) messages for m less or equal the value of this flag. crank it and watch the lore spill out. 🔥
heads up bestie: --stderrthreshold is <threshold, default: 2> and --minloglevel is <level, default: 0> — the severity numbers are the same in both, don't get it twisted. 💀

⭐ EXAMPLES ⭐

starting the service with a gps and a skyhook provider, exposing it on the system bus:

$ /usr/bin/lomiri-location-service/examples/service
    --bus system
    --provider gps::Provider
    --provider skyhook::Provider
    --skyhook::Provider::username=ut_testing
    --skyhook::Provider::realm=ut_testing.com

a slightly more verbose instance:

$ /usr/bin/lomiri-location-service/examples/service
  --logtostderr=true
  --v=5
  --bus system
  --provider gps::Provider
  --provider skyhook::Provider
  --skyhook::Provider::username=ut_testing
  --skyhook::Provider::realm=ut_testing.com

see how the second one is just the first one with --logtostderr=true and --v=5 tacked on? main character energy honestly. 🌟

Lomiri Location Service is Copyright (C) 2012 Canonical Ltd.

and that's the whole page, bestie!! this one lives in the lomiri manual and it's dated May 2013 — shoutout to the source, go off. 🫶✨💅

📦 where this page comes from