frodovdr
/
log2ram
mirror of https://github.com/azlux/log2ram.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
log2ram/install.sh

19 lines
480 B
Bash
Raw Normal View History

forget the #!
2016-04-18 12:07:33 +02:00
#!/bin/sh
sudo check
2016-04-18 14:07:20 +02:00
if [ `id -u` -eq 0 ]
then
cp log2ram.service /etc/systemd/system/log2ram.service
no x flag for logr2ram.server (#3) no x flag for logr2ram.server
2016-08-02 20:55:15 +02:00
chmod 644 /etc/systemd/system/log2ram.service
sudo check
2016-04-18 14:07:20 +02:00
cp log2ram /usr/local/bin/log2ram
I miss all chmod
2016-04-18 14:12:30 +02:00
chmod a+x /usr/local/bin/log2ram
Configuration file added
2017-05-02 00:43:37 +02:00
cp log2ram.conf /etc/log2ram.conf
chmod 644 /etc/log2ram.conf
sudo check
2016-04-18 14:07:20 +02:00
systemctl enable log2ram
Sync the ramlog back to disk, hourly. - Since the cron job could be called before the user reboots after install (or if log2ram is disabled), we check that the hdd log location exists before syncing. - Copy the log2ram.hourly sync script to cron's hourly directory on install.
2016-11-30 18:41:41 +01:00
cp log2ram.hourly /etc/cron.hourly/log2ram
chmod +x /etc/cron.hourly/log2ram
sudo check
2016-04-18 14:07:20 +02:00
echo "Reboot to activate log2ram"
Sync the ramlog back to disk, hourly. - Since the cron job could be called before the user reboots after install (or if log2ram is disabled), we check that the hdd log location exists before syncing. - Copy the log2ram.hourly sync script to cron's hourly directory on install.
2016-11-30 18:41:41 +01:00
else
sudo check
2016-04-18 14:07:20 +02:00
echo "You need to be ROOT (sudo can be used)"
fi