Useful scripts for administrators/users
Go to file
Jeremy Gardais 999bc04056 Add proxmox hook to copy a dump as a template 2016-12-09 16:08:26 +01:00
proxmox Add proxmox hook to copy a dump as a template 2016-12-09 16:08:26 +01:00
CHANGELOG First commit: 2014-09-08 09:59:12 +02:00
README.md Add proxmox hook to copy a dump as a template 2016-12-09 16:08:26 +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
mailtosesame mailtosesame: add dependancie information 2016-04-20 12:15:15 +02:00
sesame2mail Add a script to get user's mail from it's UID (LDAP UR1). 2016-07-01 14:58:06 +02:00
snapsend.sh Fix for snapsend.sh: 2014-11-21 15:10:03 +01:00
update_iso.sh First commit: 2014-09-08 09:59:12 +02: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

vzdump-hook-lxc-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:
  • Remove the templates oldest than 2 days (by default).
  • Copy the current dump as a template in /mnt/zfsbkp/template/cache (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-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.

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.