pump(1)

🌸 NAME 🌸

pump β€” accelerate remote compilation with distcc. That's it, that's the whole vibe. She's here to make your builds go zoom. πŸ’¨βœ¨


πŸŽ€ SYNOPSIS πŸŽ€

pump BUILD-COMMAND [ARGS]  ...

eval ` pump --startup `; BUILD-COMMAND [ARGS]  ...  ; pump --shutdown

πŸ’… DESCRIPTION πŸ’…

okay so. pump is part of distcc, bestie. She's the girl who runs distcc's pump mode. And what does pump mode do, you ask? It accelerates remote compilation with distcc by also distributing preprocessing to the servers. Yes queen, preprocessing too. She's not doing half the job, she's doing the whole job. πŸ’–

For a detailed description of pump mode β€” and most notably some important restrictions, no cap, please actually read those β€” go see the distcc(1) man page. Specifically the HOW PUMP-MODE WORKS section and the RESTRICTIONS ON PUMP MODE section. iykyk. πŸ“–

The simplest usage is the form

pump COMMAND [ARG]  ...

So what happens here: she'll start an include server for distcc's "pump" mode; optionally run lsdistcc to compute the distcc host list; set some auxiliary environment variables; change PATH to use the distcc client in the same directory as the "pump" script; execute COMMAND with the specified ARG(s); and then shut down the include server. Whew. She did all that. πŸ’…

The COMMAND is typically a parallel build command, such as "make -j80", that will do many concurrent invocations of distcc. Parallel build energy. Main character build energy. πŸƒβ€β™€οΈπŸƒβ€β™€οΈπŸƒβ€β™€οΈ

An alternative way of invoking pump is to explicitly invoke "pump --startup" to start the include server and "pump --shutdown" to stop the include server. The "pump --startup" command will start up the include server, and will print out some environment variable settings. These environment variables are used to communicate between the pump-mode "distcc" client and the include server, and to communicate between "pump --startup" and "pump --shutdown". The caller of "pump --startup" is responsible for setting those environment variables before invoking "distcc" or "pump --shutdown". That's on you, bestie β€” she printed them, you gotta set them. 🫢

For example:

eval `pump --startup`
make -j80
pump --shutdown
⚠️ Note that distcc's pump-mode assumes that source files will not be modified during the lifetime of the include server, so modifying source files during a build may cause inconsistent results. Like, don't do it. She's begging. 😭

πŸ” INVOKING LSDISTCC πŸ”

When invoked in either the simple " pump COMMAND [ARG] ... " form, or as " pump --startup ", the pump script will invoke lsdistcc whenever DISTCC_POTENTIAL_HOSTS is set and DISTCC_HOSTS isn't. She'll pass the value of DISTCC_POTENTIAL_HOSTS to lsdistcc and use the output of lsdistcc to set DISTCC_HOSTS. Automatic. Iconic. ✨


⭐ OPTIONS ⭐

  • --help β€” Displays summary instructions. She's telling you how she works. Listen. πŸ‘‚
  • --startup β€” Starts an include server, and outputs the environment variable settings needed for distcc(1) or pump --shutdown to access it. πŸ”₯
  • --shutdown β€” Shuts down an include server started up by pump --startup. Bye bestie, closing the door behind you. πŸšͺπŸ’œ

🌈 ENVIRONMENT VARIABLES 🌈

The following environment variables are all optional. Every single one. No pressure. 🧚

  • DISTCC_LOCATION β€” The location of the distcc bin directory, which is normally inferred from the link-resolved dirname of argv[0]. If this location is in fact the bin directory inside an installation (as will be the case when the pump script in the installation executes), then Python executables and distcc itself will be retrieved from the parent directory of the location. πŸ—‚οΈ
  • DISTCC_MAX_DISCREPANCY β€” see the distcc(1) man page. She's not repeating herself, go read it. πŸ“š
  • DISTCC_POTENTIAL_HOSTS β€” The distcc servers that will be queried by lsdistcc in order to produce a value for DISTCC_HOSTS. This value may be unset or null. In such cases, lsdistcc will not be invoked, and distcc will use DISTCC_HOSTS or the distcc hosts configuration file, as described in the "Host Specifications" section of distcc(1). 🌐
  • DISTCC_HOSTS β€” This variable is passed through to distcc but only if DISTCC_POTENTIAL_HOSTS is not set. Conditional queen. πŸ‘‘
  • LSDISTCC_ARGS β€” Extra arguments to pass to lsdistcc. See lsdistcc --help for more details. 🎁
  • INCLUDE_SERVER_ARGS β€” Extra arguments to pass to the include server. πŸ“¦
  • PYTHONOPTIMIZE β€” If set to "", then Python optimization is disabled. Literally the empty string. Not "0", not "false". "". πŸ’€

πŸ¦‹ EXAMPLE πŸ¦‹

pump make -j20

twenty jobs. twenty. slay. πŸ”₯πŸ”₯πŸ”₯


πŸ’€ BUGS πŸ’€

If you think you have found a distcc bug, please see the file reporting-bugs.txt in the documentation directory for information on how to report it. She wants to hear about it, fr fr. πŸ›


πŸ’– AUTHORS πŸ’–

The pump script and distcc's pump mode were written by Nils Klarlund, Manos Renieris, Fergus Henderson, and Craig Silverstein. Legends, all of them. Please report bugs to <distcc@lists.samba.org>. πŸ“§


πŸŽ€ LICENCE πŸŽ€

pump is part of distcc. You are free to use distcc. distcc (including this manual) may be copied, modified or distributed only under the terms of the GNU General Public Licence version 2 or later. distcc comes with absolutely no warranty. A copy of the GPL is included in the file COPYING. βš–οΈ


🌟 SEE ALSO 🌟

distcc(1), distccd(1), include_server(1), gcc(1), and make(1)


and that's the whole page, bestie πŸ’– this one's from the General Commands Manual, it's pump(1), and it was dated 9 June 2008 β€” yeah, she's an elder but she still eats. periodt. βœ¨πŸ’…πŸ«Ά