The state of chopchop on {{now}}?
tldr@chopchop:~ $whoami
{{device_info}}
{{chopchop}}
{{ip_address}}
XPUB 1 users use chopchop as a shared community server. chopchop is usually located in the Piet Zward Wijnhaven building, although for this occassion it is resting on the shelf bellow this e-reader.tldr@chopchop:~ $uptime -sUptime 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.
{{ since_last_boot }}
{% if since_last_boot is defined %} {% if days_since_last_boot|int > 14 %}This is unusual, we are used to our server crashing quite often, especially when we are all sharing the space and editing at the same time. Our server, chopchop, chops up time into small bits of surprise in which we learn that the technologies we rely on are never just up and running on their own. They require people to care for them, to put in the time and the mindspace to figure out how to keep them running and available.{% else %}This 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.{% endif %} {% endif %}tldr@chopchop:~ $sudo journalctl -S today _COMM=useradd -rUsers 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. {% if users_created_today is defined %} {% if users_created_today|length > 0 %}{{last_user_name}} user was added, and the network of trust grew ever so slightly. Users will be trusted with not just the keys and passwords to the "house" which is the server, but with a portion of responsibility to keep it afloat and contribute to what makes it a community of practices (and network of knowledge and dependence). {% endif %} {% if users_created_today|length < 0 %} No new users were created today. The trust network remains the dame size.{% endif %} {% endif %} {% if list_package_installs|length > 0 %}
tldr@chopchop:~ $ grep 'install' /var/log/dpkg.log
-
Today the following packages were installed:
{% for item in list_package_installs %}
- {{ item }} {% endfor %} Packages are often installed to use different software or coding languages or build alternative tools. Often users have to talk about and consider which packages they need and why, as well as how much storage they take up and how they will change their interactions with and on their shared server.
tldr@chopchop:~ $ grep 'upgrade' /var/log/dpkg.logOut of the installed packages, these ones were upgraded:
-
{% for item in list_package_upgrade %}
- {{ item }} {% endfor %} Packages are upgraded to fix previous bugs they had, or allow new options for usage they did not have prior.
tldr@chopchop:~ $ grep 'remove' /var/log/dpkg.logThese package were removed today:
-
{% for item in list_package_remove %}
- {{ item }} {% endfor %} Packages could be removed because of consuming too much storage, not being used by the people who share the server, or they are no longer secure. It is often good practice to 'do some spring cleaning' every now and then and remove the packages that no longer serve you any purpose.
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.
{% if logins_today is defined %}
-
{% for item in logins_today %}
- {{ item }} {% endfor %}
tldr@chopchop:~ $sudo journalctl _COMM=groupadd -r --output-fields=MESSAGEThis command shows whether groups were added today.
-
{% for item in groups_created %}
- {{ item }} These new working groups were added today. They might be used for creating new projects, maintaining or managing parts of the server, or for organizational purposes. {% endfor %}
tldr@chopchop:~ $sudo journalctl _COMM=groupremove -r --output-fields=MESThis command shows whether groups were removed today.
-
{% for item in groups_removed %}
- {{ item }} These new groups were removed today. Most likely they were no longer relevant or purposeful. {% endfor %}
tldr@chopchop:~ $sudo journalctl _COMM=usermod -rThis command shows whether users were modified today.
-
{% for item in user_modified %}
- {{ item }} These users have been modified. Probably because someone changed their password, keys, or other settings, or given new permissions. {% endfor %}
tldr@chopchop:~ $sudo journalctl _COMM=userdel -rThis command shows whether users were removed today.
-
{% for item in user_deleted %}
- {{ item }} It seems that a user was removed. This doesn't happen too often... It could be that they have done something to lose the trust of the community. The circle of trust shrunk ever so slightly. {% endfor %}
tldr@chopchop:~ $sudo service --status-allAll of the service that are active running, + running, - idle, not running.
-
{% for item in list_active_services %}
- {{ item }} {% endfor %}
tldr@chopchop:~ $sudo journalctl -S today -u kitchen-stove.service -u
kitchen-bin.service -u kitchen-fridge.service -r -n
{% if kitchen_services|length > 0 %}
-
{% for item in kitchen_services %}
- {{ item }} {% endfor %}