Hi Bernardo
You could try looking at the main system log by using the tail
command. For example...
In a terminal.. type the following line.
tail /var/log/syslog
See if that give you any clues. You could try adding -100 to the
command to display the last 100 lines of information.
tail -100
On Sunday 12 October 2014 04:08:41 pm Geoff Barkman wrote:
tail /var/log/syslog
Better yet,
tail -f /var/log/logname ( can be any file, actually )
( -f = follow )
That way, the entries will be displayed as they are created.
No, it's not real time ( very little actually is ) but it'll
I've configured RD to be able to import logs from a third party and it
works well, with the following exception. I cannot get the any clock to
stick in the grid from Thurs 1300 to Sun 2300. They refuse to stick whether
I do them manually or a Change All. I do get the following error in the
syslog.
Hi,
Easiest way is to change the services table to MyISAM
ALTER TABLE `SERVICES` ENGINE=MyISAM;
In theory innodb is less likely to lose data during a power outage and
you can do funky stuff with MariaDB and clustering if you use Innodb but
in reality you can't really use Riv without MyISAM
Thanks Wayne,
Did the trick, backup the database, made the change and voila.
Appreciate the fast response.
Regards, Richard
On Sun, Oct 12, 2014 at 7:09 PM, Wayne Merricks
waynemerri...@thevoiceasia.com wrote:
Hi,
Easiest way is to change the services table to MyISAM
ALTER TABLE
