__ __ __ __ _____ _ _ _____ _ _ _ | \/ | \ \ / / | __ \ (_) | | / ____| | | | | | \ / |_ __\ V / | |__) | __ ___ ____ _| |_ ___ | (___ | |__ ___| | | | |\/| | '__|> < | ___/ '__| \ \ / / _` | __/ _ \ \___ \| '_ \ / _ \ | | | | | | |_ / . \ | | | | | |\ V / (_| | || __/ ____) | | | | __/ | | |_| |_|_(_)_/ \_\ |_| |_| |_| \_/ \__,_|\__\___| |_____/|_| |_|\___V 2.1 if you need WebShell for Seo everyday contact me on Telegram Telegram Address : @jackleetFor_More_Tools:
#!/bin/sh set -e # Packages including pam configurations need to include a block like # the following to arrange for removal of the PAM profile prior to # package removale. Libpam-runtime is special because it includes the # machinery for managing the profiles and because there is a check to # make sure at least one profile is enabled. Libpam-runtime can only # be removed in a situation where dpkg checks are being overriden; in # that case the resulting PAM config is likely to be broken anyway. # But we prefer to permit the removal if enough dpkg force options are # given than to create an infinite loop. So, this block is commented # out, left here as an example for other packages. # if [ "$1" = remove ] ; then # pam-auth-update --package --remove unix # fi