ianmclinden / motd-rs

Dynamic MOTD generation for all platforms

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

motd-rs

Dynamic MOTD generation, written in rust. Inspired by Ubuntu's update-motd.


Best Practices

Based on Ubuntu Manpages/update-motd

MOTD fragments must be scripts in <PREFIX>/etc/update-motd.d/, must be executable, and must emit information on standard out.

Scripts should be named named NN-xxxxxx where NN is a two digit number indicating their position in the MOTD, and xxxxxx is an appropriate name for the script.

Scripts must not have filename extensions, per run-parts(8) --lsbsysinit instructions.

Users should add scripts directly into <PREFIX>/etc/update-motd.d/, rather than symlinks to other scripts, such that administrators can modify or remove these scripts and upgrades will not wipe the local changes. Consider using a simple shell script that simply calls exec on the external utility.

Long running operations (such as network calls) or resource intensive scripts should cache output, and only update that output if it is deemed expired. For instance:

#!/bin/sh
out=/var/run/foo
script="w3m -dump http://news.google.com/"
if [ -f "$out" ]; then
    # Output exists, print it
    echo
    cat "$out"
    # See if it's expired, and background update
    lastrun=$(stat -c %Y "$out") || lastrun=0
    expiration=$(expr $lastrun + 86400)
    if [ $(date +%s) -ge $expiration ]; then
        $script > "$out" &
    fi
else
    # No cache at all, so update in the background
    $script > "$out" &
fi

Scripts should emit a blank line before output, and end with a newline character. For instance:

#!/bin/sh
echo
lsb-release -a

Environment

The PREFIX environment variable describes the the path prefix, whichs is combined with the /etc/update-motd.d/ resulting in the directory containing MOTD fragments. Defaults to /, resulting in /etc/update-motd.d/ as in Ubuntu.

To customize this, for example to use the macOS (with intel) standard prefix /usr/local, compile with the PREFIX set:

PREFIX="/usr/local" cargo build

Or more genenrally, to use the homebrew prefix for a platfor, compile with:

PREFIX="$(brew --prefix)" cargo build

Installation / Usage

Build and install motd with cargo, and create the MOTD directory

cargo install --path .
# Or, with a custom PREFIX, e.g. for macOS (with homebrew)
# PREFIX="$(brew --prefix)" cargo install --path .
mkdir -p $(motd --path)

Then, add motd to your profile (for interactive login shells).

# E.g. for bash
echo -e "# Dynamic MOTD\n[[ -e \"$(which motd)\" ]] && $(which motd)" >>  ~/.bash_profile

Tools

Additional tools are included that provide platform-specific capabilities. Currently only macOS tools are available.

Build and install these tools with cargo:

# on macOS
cargo install --path tools/macOS
# Or, with a custom PREFIX, e.g. for macOS (with homebrew)
# PREFIX="$(brew --prefix)" cargo install --path tools/macOS

Sample MOTD Fragments

A few basic MOTD fragments are provided, currently for ubuntu and macOS.

To include some these samples, copy the included /samples/<os> to <PREFIX>/etc/update-motd.d/:

# On macOS
install -D -m 0755 samples/macOS/* -t $(motd --path)
# On Ubuntu
install -D -m 0755 samples/ubuntu/* -t $(motd --path)

LICENSE

This program is licensed under the GNU General Public License v3.0 or later license. See LICENSE for full license text.

About

Dynamic MOTD generation for all platforms

License:GNU General Public License v3.0


Languages

Language:Rust 100.0%