BOS_STARTUP(8)

📦
version 1.8.16.1 · 10 versions
, in ubuntu stonking

💖 BOS_STARTUP 💖

okay so bestie, welcome to bos_startup, live from the AFS Command Reference (section 8 of the manual, if you're keeping score 🎀). Sit down, grab a strawberry 🍓, and let's talk about starting processes without touching their little status flag.

✨ NAME ✨

bos_startup — starts a process without changing its status flag 👑

🌸 SYNOPSIS 🌸

bos startup -server <machine name> [-instance <instances>+]
    [-cell <cell name>] [-noauth] [-localauth] [-help]

bos startu -s <machine name> [-i <instances>+]
    [-c <cell name>] [-n] [-l] [-h]

🦋 DESCRIPTION 🦋

The bos startup command starts stuff, on the server machine you name with the -server argument. And it starts exactly one of these two things:

  • Every AFS server process that isn't currently running but is marked with the "Run" status flag in the /etc/openafs/BosConfig file.
  • Each process you name with the -instance argument — yes, even if its status flag in the BosConfig file says "NotRun". Iconic. It does not care. 💅
now listen, this is the important part: if you want to start a process and flip its BosConfig status flag to "Run", that's a whole different command. Go use bos start for that instead. bos startup is out here leaving flags exactly where it found them. no cap.

💅 OPTIONS 💅

  • -server <machine name> — tells you which server machine to start processes on. ID the machine with an IP address or its host name (fully-qualified, or abbreviated as long as it's unambiguous). More deets over in bos(8). 🖥️
  • -instance <instances>+ — names each process to start. Use the process name you assigned with the -instance argument to the bos create command. And if you forgot the names? bos status output lists them for you, slay. 📋
  • -cell <cell name> — names the cell to run the command in. Do not combine this with the -localauth flag, they are NOT compatible okay. More details in bos(8). 🏠
  • -noauth — hands the issuer the unprivileged identity "anonymous". Do not combine this flag with -localauth, seriously, they fight. More details in bos(8). 🙈
  • -localauth — constructs a server ticket using a key from the local /etc/openafs/server/KeyFile or /etc/openafs/server/KeyFileExt file. The bos command interpreter then presents that ticket to the BOS Server during mutual authentication. Do not combine this flag with the -cell or -noauth options. More details in bos(8). 🔑
  • -help — prints the online help for this command. Every other valid option gets ignored, periodt. ❓

🌈 EXAMPLES 🌈

First up: this one starts all the processes marked with status flag "Run" in the BosConfig file on the machine "fs3.example.com" that aren't currently running. 🏃‍♀️

% bos startup fs3.example.com

And this one starts the buserver, kaserver, ptserver, and vlserver processes running on the machine "db2.example.com" — even if their status flags in the BosConfig file say "NotRun". Main character energy fr fr. 🔥

% bos startup -server db2.example.com \
    -instance buserver kaserver ptserver vlserver

👑 PRIVILEGE REQUIRED 👑

The issuer has to be listed in the /etc/openafs/server/UserList file on the machine named by the -server argument. OR — alternative route — they must be logged onto a server machine as the local superuser "root" if the -localauth flag is included. that's the whole vibe check, bestie. 💜

🔗 SEE ALSO 🔗

BosConfig(5), KeyFile(5), KeyFileExt(5), UserList(5), bos(8), bos_create(8), bos_start(8), bos_status(8)

go read them, iykyk 🧚

IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved.

This documentation is covered by the IBM Public License Version 1.0. It was converted from HTML to POD by software written by Chas Williams and Russ Allbery, based on work by Alf Wachsmann and Elizabeth Cassell.

and that's the whole page, angel 🫶 this edition of the OpenAFS manual dropped on 2026-07-27, and it's filed under BOS_STARTUP(8) forever and ever. stay slaying, go start some processes, and remember: leave those status flags alone 💖✨🎀

📦 where this page comes from