Anyone with a PAM account and Sys.Console access could have started a termproxy session, adapt the regex. Always test for broken entries and run the sed expression to make sure eventually all occurences of the broken syntax are fixed. Signed-off-by: Stefan Reiter <s.reiter@proxmox.com>
		
			
				
	
	
		
			35 lines
		
	
	
		
			903 B
		
	
	
	
		
			Bash
		
	
	
	
	
	
			
		
		
	
	
			35 lines
		
	
	
		
			903 B
		
	
	
	
		
			Bash
		
	
	
	
	
	
#!/bin/sh
 | 
						|
 | 
						|
set -e
 | 
						|
 | 
						|
#DEBHELPER#
 | 
						|
 | 
						|
case "$1" in
 | 
						|
    configure)
 | 
						|
	# modeled after dh_systemd_start output
 | 
						|
	systemctl --system daemon-reload >/dev/null || true
 | 
						|
	if [ -n "$2" ]; then
 | 
						|
		_dh_action=try-reload-or-restart
 | 
						|
	else
 | 
						|
		_dh_action=start
 | 
						|
	fi
 | 
						|
	deb-systemd-invoke $_dh_action proxmox-backup.service proxmox-backup-proxy.service >/dev/null || true
 | 
						|
 | 
						|
	# FIXME: Remove in future version once we're sure no broken entries remain in anyone's files
 | 
						|
	if grep -q -e ':termproxy::[^@]\+: ' /var/log/proxmox-backup/tasks/active; then
 | 
						|
	    echo "Fixing up termproxy user id in task log..."
 | 
						|
	    flock -w 30 /var/log/proxmox-backup/tasks/active.lock sed -i 's/:termproxy::\([^@]\+\): /:termproxy::\1@pam: /' /var/log/proxmox-backup/tasks/active
 | 
						|
	fi
 | 
						|
    ;;
 | 
						|
 | 
						|
    abort-upgrade|abort-remove|abort-deconfigure)
 | 
						|
    ;;
 | 
						|
 | 
						|
    *)
 | 
						|
        echo "postinst called with unknown argument \`$1'" >&2
 | 
						|
        exit 1
 | 
						|
    ;;
 | 
						|
esac
 | 
						|
 | 
						|
exit 0
 |