Useful scripts for administrators/users
Go to file
Jeremy Gardais 0bb95412a2 Add a script to remount devices with extra rights
To be able to run updates such as apt, dpkg, grub,…
2018-03-12 13:47:53 +01:00
proxmox Need to escape a backslash 2018-02-21 09:45:38 +01:00
CHANGELOG First commit: 2014-09-08 09:59:12 +02:00
README.md Add a script to prepare a container to becoming a debian template 2018-02-13 13:58:04 +01:00
TODO.md sesame2mail: can now convert one user ID passed in arg to it's mail address 2017-01-17 18:27:37 +01:00
block_list.sh Small script to parse fail2ban's log files and extract the IP banned in 2014-12-05 10:25:23 +01:00
copy_to_usb.sh Rename fullusb.sh to copy_to_usb.sh 2016-09-15 15:29:29 +02:00
grav_cron Add grav daily cron to check available update. 2016-10-26 14:59:05 +02:00
ldap1_connection.sh ldap1_connection: add a white space after the port number (389) to avoid ports like "38965" … 2016-04-20 12:15:15 +02:00
mail2sesame rename mailtosesame -> mail2sesame 2017-03-06 10:07:59 +01:00
remountdefault Add a script to remount devices with default value 2018-03-12 10:49:33 +01:00
remountrw Add a script to remount devices with extra rights 2018-03-12 13:47:53 +01:00
sesame2mail Add "read -r" 2017-02-15 14:38:32 +01:00
snapsend.sh Fix for snapsend.sh: 2014-11-21 15:10:03 +01:00
update_iso.sh Use $() instead of `` 2017-02-15 14:39:37 +01:00
wordpress_cron Ensure to use the right command to check core update ! 2017-02-15 16:11:56 +01:00
zfSnap.sh Add zfSnap script from the legacy branch of the github project: 2014-11-18 16:06:51 +01:00

README.md

ipr_scripts

Table of Contents

  1. Overview
  2. Scripts

Overview

Some usefull scripts for admin or users.

Scripts

Proxmox

proxmox.template.debian.sh

Some commands in order to clean and prepare a container to become a template.

  1. The script will:
  • Allow root's connection to SSH with password.
  • Reconfigure timezone to Europe/Paris.
  • Reconfigure locales to en_US.UTF-8.
  • Download an additionnal script use by our preseed with PXE to configure logs (rsyslog, logrotate,…).
  • Remove x11 useless packages.
  • Clean some stuff (downloaded packages, empty logs,…).
  1. How-to use:
wget https://git.ipr.univ-rennes1.fr/cellinfo/scripts/raw/master/proxmox/proxmox.template.debian.sh -O /tmp/proxmox.template.debian.sh
chmod +x /tmp/proxmox.template.debian.sh
/tmp/proxmox.template.debian.sh

vzdump-hook-lxc-stretch-template.pl

This script must be used as a vzdump's hook (the backup utility for CT and VMs for Proxmox).

  1. The script will:
  • Copy the current dump as a template in /mnt/zfsbkp/template/cache (by default).
  • Unlink $TEMPLATE_FILE_LINK.
  • Link $TEMPLATE_FILE_LINK to the last dump in order to have a better name.
  • Remove the templates oldest than 2 days (by default).
  1. How-to use:
  • Define a backup as usual (in the Proxmox's webgui) and prefer to select only one container.
  • In command on the hypervisor, open /etc/pve/vzdump.cron and edit the line of the new dump to add: --script /usr/local/bin/vzdump-hook-lxc-stretch-template.pl.
  1. Customization:
  • If you don't store template in the default path (/mnt/zfsbkp/template/cache), please edit the variable $TEMPLATE_DIR in the script.
  • You might want to set another template name, please edit the variable $TEMPLATE_FILE_LINK in the script.

vzdump-hook-lxc-jessie-template.pl

Same as above but set jessie in $TEMPLATE_FILE_LINK.

Grav

grav_cron

A daily cron to check if Grav got available updates.

  • It need to work from the Grav's root directory.
  • If an update is available, it will create a empty file (${GRAV_ROOT}/logs/update), else it will ensure the "update" file is removed.
    • Be sure to monitore if ${GRAV_ROOT}/logs/update exist.

Sesame2mail

Give a user's mail address from it's user ID (sesame).

The first argument can be:

  • A file with a list of user ID (sesame), one per line.
  • A user ID (sesame), only one.

WordPress

wordpress_cron

A daily cron to check WordPress's Core and plugins updates.

  • It need [wp-cli][wp-cli website] tool.
  • If an update is available, it will create a empty file ({WP_ROOT}/.update_core or {WP_ROOT}/.update_plugin), else it will ensure the "update" files are absents.
    • So, be sure to monitore if the files ${WP_ROOT}/.update_* exists!