Mini File Manager

ZSec File Manager

Current Directory: /home/aiessinternational.com/public_html

[Up]

.. [Open]

.htaccess [Edit]

21cbfe [Open]

ALFA_DATA [Open]

advance [Open]

advance.zip [Edit]

ammika.php [Edit]

c8aa5 [Open]

click.php [Edit]

defaults.php [Edit]

google41b982abb0d9ca3b.html [Edit]

index.php [Edit]

index.php0 [Edit]

item.php [Edit]

license.txt [Edit]

mah.php [Edit]

networks.php [Edit]

options.php [Edit]

plugins.php [Edit]

product.php [Edit]

readme.html [Edit]

robots.txt [Edit]

saiga.php [Edit]

search.php [Edit]

web.config [Edit]

wp-activate.php [Edit]

wp-admin [Open]

wp-blog-header.php [Edit]

wp-comments-post.php [Edit]

wp-config-sample.php [Edit]

wp-config.php [Edit]

wp-content [Open]

wp-cron.php [Edit]

wp-includes [Open]

wp-links-opml.php [Edit]

wp-load.php [Edit]

wp-log1n.php [Edit]

wp-mail.php [Edit]

wp-settings.php [Edit]

wp-signup.php [Edit]

wp-trackback.php [Edit]

wp.php [Edit]

xmlrpc.php [Edit]

Edit File

# Templated service file for redis-server(1)
#
# Each instance of redis-server requires its own configuration file:
#
#   $ cp /etc/redis/redis.conf /etc/redis/redis-myname.conf
#   $ chown redis:redis /etc/redis/redis-myname.conf
#
# Ensure each instance is using their own database:
#
#   $ sed -i -e 's@^dbfilename .*@dbfilename dump-myname.rdb@' /etc/redis/redis-myname.conf
#
# We then listen exlusively on UNIX sockets to avoid TCP port collisions:
#
#   $ sed -i -e 's@^port .*@port 0@' /etc/redis/redis-myname.conf
#   $ sed -i -e 's@^$# $\{0,1\}unixsocket .*@unixsocket /var/run/redis-myname/redis-server.sock@' /etc/redis/redis-myname.conf
#
# ... and ensure we are logging, etc. in a unique location:
#
#   $ sed -i -e 's@^logfile .*@logfile /var/log/redis/redis-server-myname.log@' /etc/redis/redis-myname.conf
#   $ sed -i -e 's@^pidfile .*@pidfile /run/redis-myname/redis-server.pid@' /etc/redis/redis-myname.conf
#
# We can then start the service as follows, validating we are using our own
# configuration:
#
#   $ systemctl start redis-server@myname.service
#   $ redis-cli -s /var/run/redis-myname/redis-server.sock info | grep config_file
#
#  -- Chris Lamb <lamby@debian.org>  Mon, 09 Oct 2017 22:17:24 +0100
[Unit]
Description=Advanced key-value store (%I)
After=network.target
Documentation=http://redis.io/documentation, man:redis-server(1)

[Service]
Type=notify
ExecStart=/usr/bin/redis-server /etc/redis/redis-%i.conf --supervised systemd --daemonize no
PIDFile=/run/redis-%i/redis-server.pid
TimeoutStopSec=0
Restart=always
User=redis
Group=redis
RuntimeDirectory=redis-%i
RuntimeDirectoryMode=2755

UMask=007
PrivateTmp=yes
LimitNOFILE=65535
PrivateDevices=yes
ProtectHome=yes
ReadOnlyDirectories=/
ReadWritePaths=-/var/lib/redis
ReadWritePaths=-/var/log/redis
ReadWritePaths=-/var/run/redis-%i

NoNewPrivileges=true
CapabilityBoundingSet=CAP_SETGID CAP_SETUID CAP_SYS_RESOURCE
MemoryDenyWriteExecute=true
ProtectKernelModules=true
ProtectKernelTunables=true
ProtectControlGroups=true
RestrictRealtime=true
RestrictNamespaces=true
RestrictAddressFamilies=AF_INET AF_INET6 AF_UNIX

# redis-server can write to its own config file when in cluster mode so we
# permit writing there by default. If you are not using this feature, it is
# recommended that you replace the following lines with "ProtectSystem=full".
ProtectSystem=true
ReadWriteDirectories=-/etc/redis

[Install]
WantedBy=multi-user.target