TD;DR_March_26th_2024

html makers

Preface

TL;DR researches ways to make sense of the hidden labour that goes on in a feminist server through log files and unlogged activity.

The unlogged activity of a server includes the physical labour, the decisions about shared spaces, the different knowledges that depend on each other for the network to exis

Activity that is logged, is often compiled in inaccessible log files that track the work a server performs as data. They're both hard to retrieve, hard to decipher, and have a bias towards the technological ecology, prioritizing the labour of machines.

Chopchop is a a Raspebrry Pi that is configured, maintained and used by XPUB1 as a community server.

Chopchop is a a Raspberry Pi that is configured, maintained and used as a community server by XPUB1

This EPUB is a generated compilation of logs with annotations that provide context to the situatedness of this technology. With one book a day, a diary of chopchop is kept, stored and shared.

The state of chopchop on 2024-03-26 14:21:11.735374?

tldr@chopchop:~ $whoami

Raspberry Pi 4 Model B Rev 1.4

192.168.1.87

XPUB 1 users use chopchop as a shared community server. chopchop is usually located in the Piet Zwart Wijnhaven building, although for this occassion it is resting on the shelf bellow this e-reader.

tldr@chopchop:~ $uptime -s

Uptime is the amount of time a server has been up, available, running, working, executing. This is time that is not spent idle, but time spent busy serving.

2024-03-26 09:12:16

This short of an uptime is common, the fragility of these machines are more prominent than any cloud user expects. Partially because of scale, partially because a lot of labour that happens in datacenters just escapes us all when we want to just upload an image, or just send a message, or just open a webpage.

tldr@chopchop:~ $sudo journalctl -S today _COMM=useradd -r

Users are assigned to groups, which allow them rights to read or edit files, run commands or apply infrastructural changes. For chopchop, we all have 'sudo rights': the ability to perform any command, including the more sensitive ones. Sudo is a command that's short for 'superuser do', with it, a user has more privileges, like installing or updating a package or performing a restart.

tldr@chopchop:~ $ grep 'install' /var/log/dpkg.log

Something here in the if statement is not working

2024-03-26 13:54:58 status installed sl:armhf 5.02-1

2024-03-26 13:54:59 status half-installed sl:armhf 5.02-1

2024-03-26 13:54:59 status not-installed sl:armhf

2024-03-26 13:55:00 status installed man-db:armhf 2.11.2-2

2024-03-26 13:55:09 install sl:armhf 5.02-1

2024-03-26 13:55:09 status half-installed sl:armhf 5.02-1

2024-03-26 13:55:10 status installed sl:armhf 5.02-1

2024-03-26 13:55:10 status installed man-db:armhf 2.11.2-2

tldr@chopchop:~ $ grep 'remove' /var/log/dpkg.log

These package were removed today:

2024-03-26 13:54:58 startup packages remove

2024-03-26 13:54:59 remove sl:armhf 5.02-1

These actions are only a portion of the work... There's also the relationships of the people who care for the server enough to maintain it... The hours they put into meeting each other, discussing and deciding on how to move forward... They are sharing a digital landscape in which there are no hierarchies of landlords and renters... So, they find different ways to make a space for learning and co-habitation... This list is not exhaustive.

tldr@chopchop:~ $sudo journalctl _COMM=systemd-login
    --output-fields=MESSAGE -S today -g "New session" | grep -v 'Boot'

Users can login to the server using the SSH (secure shell) protocol. This allows a user to explore files, make changes, run commands and speak to the server from their own machine. This is useful when working remotely, and also to allow multiple users logging into the server simultaneously. Current XPUB1 students have a chopchop user, as well as the tutors. Additionally, there are some users not associated with a person, like our shared user 'chipchip' and users for running specific processes or creating projects.

does not show the users of logins_today These users have logged into our shared server chopchop, during the course of this day. For some reason this if statement is not working, i didn't apply it to the next 4 categories because i wanted to check it works first

tldr@chopchop:~ $sudo journalctl _COMM=groupremove -r --output-fields=MES

This command shows whether groups were removed today.

tldr@chopchop:~ $sudo journalctl _COMM=usermod -r

This command shows whether users were modified today.

tldr@chopchop:~ $sudo journalctl _COMM=userdel -r

This command shows whether users were removed today.

tldr@chopchop:~ $sudo service --status-all

These are all of the services that are active, running, working to execute requests that enable everything on the server. They are marked with an [+]. The rest, marked with a [-], are idle, not running, or waiting to be activating upon sending a request.

[ - ] alsa-utils

[ - ] apparmor

[ + ] atop

[ + ] atopacct

[ + ] bluetooth

[ - ] console-setup.sh

[ + ] cron

[ + ] cups

[ + ] cups-browsed

[ + ] dbus

[ + ] dphys-swapfile

[ + ] exim4

[ + ] fake-hwclock

[ - ] fcgiwrap

[ - ] hwclock.sh

[ + ] incron

[ - ] keyboard-setup.sh

[ + ] kmod

[ + ] networking

[ - ] nfs-common

[ + ] nginx

[ - ] paxctld

[ - ] php7.4-fpm

[ + ] php8.2-fpm

[ + ] procps

[ - ] pulseaudio-enable-autospawn

[ + ] raspi-config

[ + ] rng-tools-debian

[ - ] rpcbind

[ - ] rsync

[ - ] saned

[ + ] ssh

[ - ] sudo

[ + ] triggerhappy

[ + ] udev

[ - ] uuidd

[ - ] x11-common

tldr@chopchop:~ $sudo journalctl -S today -u kitchen-stove.service -u
      kitchen-bin.service -u kitchen-fridge.service -r -n

Mar 26 14:21:11 chopchop systemd[1]: Started kitchen-fridge.service - Kitchen Fridge Service.

Mar 26 14:21:11 chopchop systemd[1]: Stopped kitchen-fridge.service - Kitchen Fridge Service.

Mar 26 14:21:11 chopchop systemd[1]: kitchen-fridge.service: Scheduled restart job, restart counter is at 8226.

Mar 26 14:21:10 chopchop systemd[1]: kitchen-fridge.service: Failed with result 'exit-code'.

Mar 26 14:21:10 chopchop systemd[1]: kitchen-fridge.service: Main process exited, code=exited, status=1/FAILURE

Mar 26 14:21:10 chopchop python3[27335]: EOFError: EOF when reading a line

Mar 26 14:21:10 chopchop python3[27335]: ^^^^^^^

Mar 26 14:21:10 chopchop python3[27335]: answer = input()

Mar 26 14:21:10 chopchop python3[27335]: File "/home/chef/kitchen/fridge/Fridge.py", line 36, in main

Mar 26 14:21:10 chopchop python3[27335]: main()