15 Commits

Author	SHA1	Message	Date
Nathan Huizinga	4f7c1a33a2	Bug fix: avoid installing when still installed	2017-12-16 11:42:37 +01:00
Nathan Huizinga	0e76e8d655	Fixed: supporting a previous log2ram version again	2017-12-11 08:55:38 +01:00
Nathan Huizinga	658161bb04	Fixed consistent naming of /var/hdd.log	2017-12-07 17:42:40 +01:00
azlux	a31ba4927f	Remove old folder	2017-10-02 20:48:02 +02:00
azlux	b7c725f47d	Fix for #28 ... The init is useless and the mount was async.	2017-10-02 20:37:46 +02:00
azlux	bd1b669ed9	Stupid I am ... Log on disk wasn't copy on install, so the shutdown destroy everything. #18 #17	2017-06-11 20:59:57 +02:00
azlux	1e18687475	REBOOT after install ... It's maybe the pb of #17	2017-06-02 19:56:57 +02:00
azlux	b232b00950	bad copy/paste ?	2017-05-02 14:47:59 +02:00
azlux	a54aee856d	Configuration file added	2017-05-02 00:43:37 +02:00
Nick Daly	e238849069	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 11:41:41 -06:00
Sailing74	e50a968dce	no x flag for logr2ram.server (#3) ... no x flag for logr2ram.server	2016-08-02 20:55:15 +02:00
azlux	48980b2de2	I miss all chmod	2016-04-18 14:12:30 +02:00
azlux	f667036300	sudo check	2016-04-18 14:07:20 +02:00
azlux	873593776b	forget the #!	2016-04-18 12:07:33 +02:00
azlux	4df5b08121	Create install.sh	2016-04-18 12:06:16 +02:00