/tmp$ sudo chmod +x ./log2ram-master/install.sh && sudo ./log2ram -master/install.sh
install: cannot stat 'log2ram.service': No such file or directory
install: cannot stat 'log2ram': No such file or directory
install: cannot stat 'log2ram.conf': No such file or directory
install: cannot stat 'uninstall.sh': No such file or directory
Failed to enable unit: Unit file log2ram.service does not exist.
install: cannot stat 'log2ram.hourly': No such file or directory
install: cannot stat 'log2ram.logrotate': No such file or directory
Reboot to activate log2ram
service log2ram status
● log2ram.service - Log2Ram
Loaded: loaded (/etc/systemd/system/log2ram.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2018-01-28 15:58:30 UTC; 7 months 1 days ago
Process: 281 ExecStart=/usr/local/bin/log2ram start (code=exited, status=1/FAILURE)
Main PID: 281 (code=exited, status=1/FAILURE)
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
service log2ram start
Failed to start log2ram.service: Connection timed out
Failed to retrieve unit state: Connection timed out
Failed to stop log2ram.service: Connection timed out
See system logs and 'systemctl status log2ram.service' for details.
Failed to get load state of log2ram.service: Connection timed out
Je déconseille vivement l'installation de cet outil. La seule chose qu'il a réussi a faire c'est flinguer mon installl 18.04.1 LTS qui fait maintenant du 2 à l'heure. Mon DNS est mort, installer un simple package prend 10mn, vérifier le status de cet outil via service log2ram status met 5mn a répondre que ca ne marche pas, et la "déinstallation" fournie via le GitHub ne marche pas non plus.
# Ne fonctionne pas, la suite
Posté par Nylan . En réponse à la page de wiki [Tuto/HowTo] Transférer les logs en ram avec Log2Ram. Évalué à 1 (+0/-0).
/tmp$ sudo chmod +x ./log2ram-master/install.sh && sudo ./log2ram -master/install.sh
install: cannot stat 'log2ram.service': No such file or directory
install: cannot stat 'log2ram': No such file or directory
install: cannot stat 'log2ram.conf': No such file or directory
install: cannot stat 'uninstall.sh': No such file or directory
Failed to enable unit: Unit file log2ram.service does not exist.
install: cannot stat 'log2ram.hourly': No such file or directory
install: cannot stat 'log2ram.logrotate': No such file or directory
Reboot to activate log2ram
service log2ram status
● log2ram.service - Log2Ram
Loaded: loaded (/etc/systemd/system/log2ram.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2018-01-28 15:58:30 UTC; 7 months 1 days ago
Process: 281 ExecStart=/usr/local/bin/log2ram start (code=exited, status=1/FAILURE)
Main PID: 281 (code=exited, status=1/FAILURE)
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
service log2ram start
Failed to start log2ram.service: Connection timed out
Le meilleur pour la fin :
sudo chmod +x /usr/local/bin/uninstall-log2ram.sh && sudo /usr/local/bin/uninstall-log2ram.sh
Failed to retrieve unit state: Connection timed out
Failed to stop log2ram.service: Connection timed out
See system logs and 'systemctl status log2ram.service' for details.
Failed to get load state of log2ram.service: Connection timed out
# Ne fonctionne pas
Posté par Nylan . En réponse à la page de wiki [Tuto/HowTo] Transférer les logs en ram avec Log2Ram. Évalué à 0 (+0/-0). Dernière modification le 31 août 2018 à 11:23.
Je déconseille vivement l'installation de cet outil. La seule chose qu'il a réussi a faire c'est flinguer mon installl 18.04.1 LTS qui fait maintenant du 2 à l'heure. Mon DNS est mort, installer un simple package prend 10mn, vérifier le status de cet outil via service log2ram status met 5mn a répondre que ca ne marche pas, et la "déinstallation" fournie via le GitHub ne marche pas non plus.
Personellement c'est vraiment pas cool.