You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Based on my further testing this is NOT a bug! When I tested it initially after enabling, the ls command didn't do anything, after doing an lsattr, I see there are files in there. I was expecting a single log with the dump of the data, not small files.
Any way giving the ls command time to complete, the files are there, all 77,000+ of them. :) ;) At last count.
So with that in mind I would like to suggest that an option to TGZ the event log daily.
Thus at 0001 the next day the event log files are tar gzipped to event_log/archive/0716201.log.tgz
Thus the huge number of files in there is manageable. Yes I have a reason why I am logging this stuff. :)
Thanks.
---- Original version for archival purposes. ------
Using the latest download of sdrtrunk/JMBE, and working great for my test setup, a couple glitches:
On my main P25 system, I have events to be logged, but the ~/SDRTrunk/event_logs is not readable.
I can cd into that, but its not a directory, really, it just keeps getting bigger from being data stored from the system, but can't tail it or cat it as "cat: event_logs/: Is a directory"
*buntu 14.04 32b with:
$ java -version
java version "1.8.0_171"
Java(TM) SE Runtime Environment (build 1.8.0_171-b11)
Java HotSpot(TM) Server VM (build 25.171-b11, mixed mode)
The text was updated successfully, but these errors were encountered:
ScanCaster
changed the title
event_log is a directory and not readable
Feature Request: event_log directory archving...
Jul 17, 2018
DSheirer
changed the title
Feature Request: event_log directory archving...
Feature: event_log Directory Archving
Nov 15, 2023
Based on my further testing this is NOT a bug! When I tested it initially after enabling, the ls command didn't do anything, after doing an lsattr, I see there are files in there. I was expecting a single log with the dump of the data, not small files.
Any way giving the ls command time to complete, the files are there, all 77,000+ of them. :) ;) At last count.
So with that in mind I would like to suggest that an option to TGZ the event log daily.
Thus at 0001 the next day the event log files are tar gzipped to event_log/archive/0716201.log.tgz
Thus the huge number of files in there is manageable. Yes I have a reason why I am logging this stuff. :)
Thanks.
---- Original version for archival purposes. ------
Using the latest download of sdrtrunk/JMBE, and working great for my test setup, a couple glitches:
On my main P25 system, I have events to be logged, but the ~/SDRTrunk/event_logs is not readable.
See:
rwxrwxr-x 7 sdtrunkuser sdtrunkuser 4096 Jul 6 22:16 .
drwxr-xr-x 27 sdtrunkuser sdtrunkuser 4096 Jul 9 23:57 ..
drwxrwxr-x 2 sdtrunkuser sdtrunkuser 22736896 Jul 10 06:58 event_logs
drwxrwxr-x 2 sdtrunkuser sdtrunkuser 4096 Jul 10 00:21 logs
drwxrwxr-x 2 sdtrunkuser sdtrunkuser 4096 Jul 9 22:34 playlist
-rw-rw-r-- 1 sdtrunkuser sdtrunkuser 1282 Jul 9 00:15 SDRTrunk.properties
drwxrwxr-x 2 sdtrunkuser sdtrunkuser 4096 Jul 6 22:16 settings
drwxrwxr-x 2 sdtrunkuser sdtrunkuser 4096 Jul 10 06:58 streaming
sdtrunkuser@Z:~/SDRTrunk$ cd event_logs/
I can cd into that, but its not a directory, really, it just keeps getting bigger from being data stored from the system, but can't tail it or cat it as "cat: event_logs/: Is a directory"
*buntu 14.04 32b with:
$ java -version
java version "1.8.0_171"
Java(TM) SE Runtime Environment (build 1.8.0_171-b11)
Java HotSpot(TM) Server VM (build 25.171-b11, mixed mode)
The text was updated successfully, but these errors were encountered: