DL6ER
e75bd26994
Improve overall memory handling by checking for failed memory allocation events at the places we need the allocated space
...
Signed-off-by: DL6ER <dl6er@dl6er.de >
2018-02-07 13:23:54 +01:00
DL6ER
cf93110aee
Final fix for Travis versioning and all the cosmetic issues we have seen
...
Signed-off-by: DL6ER <dl6er@dl6er.de >
2018-01-05 22:34:07 +01:00
DL6ER
7cbf68f0b6
Output correct counters in log_counter_info() (this has always been wrong but nobody noticed it)
...
Signed-off-by: DL6ER <dl6er@dl6er.de >
2017-12-27 13:25:11 +01:00
DL6ER
538e5a3156
Handle wildcard blocked domains correctly
...
Signed-off-by: DL6ER <dl6er@dl6er.de >
2017-12-21 15:19:35 +01:00
DL6ER
32c2471e04
Check if version is of format vX.YYY or vXX.YYY to decide whether on a deployed version or not
...
Signed-off-by: DL6ER <dl6er@dl6er.de >
2017-12-07 22:42:24 +01:00
DL6ER
952024107f
Improve crash message
2017-07-07 17:55:29 +02:00
DL6ER
62804083ae
Make FTL's logging routine thread-safe ( #80 )
2017-06-15 10:47:30 +02:00
DL6ER
97f285a1a3
Remove necessity to use libmath routines
2017-04-14 18:59:39 +02:00
DL6ER
1762019d32
Use getpid() when saving PID to file
2017-04-14 17:59:01 +02:00
DL6ER
4c2124375c
Added comments
2017-04-14 17:45:56 +02:00
DL6ER
1f47f89a09
Determine exponent w/o using log10() as that caused a number of issues on various devices (returning either zero er even -NaN for valid arguments)
2017-04-14 17:40:32 +02:00
DL6ER
992f16ba56
Don't compute log of zero
2017-04-10 22:17:45 +02:00
DL6ER
8d9cd43f9d
More logging to syslog in case of critical errors
2017-04-08 22:28:34 +02:00
DL6ER
ff99ea0473
Write to SYSLOG if writing to FTL's log file fails
2017-04-08 22:24:27 +02:00
DL6ER
308c65a99f
Don't use write buffer as it might be a potential attack vector
2017-04-08 22:02:38 +02:00
DL6ER
c64ead386f
Don't fail when FTL's log cannot be opened while FTL is running (only on startup)
2017-04-08 18:56:06 +02:00
DL6ER
77ef25e4d9
Remove logg_uint and test if FTL log can be opened at start of FTL
2017-04-08 18:46:16 +02:00
DL6ER
4f5ad1f09f
Restructured logg_struct_resize
2017-04-08 18:42:07 +02:00
DL6ER
9e7a57c417
Removed logg_str_str_int
2017-04-08 18:40:34 +02:00
DL6ER
1985f8e6eb
Removed logg_str_str
2017-04-08 18:39:41 +02:00
DL6ER
5532de60b4
Removed logg_const_str
2017-04-08 18:36:30 +02:00
DL6ER
16a788429b
Removed logg_str
2017-04-08 18:34:37 +02:00
DL6ER
ece9f18c1b
Removed logg_int
2017-04-08 18:27:56 +02:00
DL6ER
5c952f2cd6
Improve flexibility of log routines
2017-04-08 18:18:07 +02:00
DL6ER
4f1df5acf7
Minor change in debug print statement
2017-04-07 14:37:59 +02:00
DL6ER
b5a28edccb
Debug mode: Print at which time query had to be enlarged (kind of log parsing process display for humongous logs
2017-04-02 22:57:23 +02:00
DL6ER
7f9229ae5a
Add application self-debugging. Also, don't silently get killed on SIGSEGV. Furthermore, try to automatically attach to the debugger on crashing (only if running in debug mode)
2017-03-31 13:18:47 +02:00
DL6ER
78f615201a
Some non-POSIX systems use different conventions for exit status values.
...
For greater portability, we now use the macros EXIT_SUCCESS and EXIT_FAILURE for the conventional status value for success and failure, respectively.
They are declared in stdlib.h
2017-03-29 14:00:51 +02:00
DL6ER
b72601b006
Print username if FTL log cannot be read
2017-03-29 13:51:25 +02:00
DL6ER
cabc6800d6
Add Query Types over Time data structure
2017-03-28 14:45:16 +02:00
DL6ER
7d0c24e360
Improve handling of structs
2017-03-17 18:43:08 +01:00
DL6ER
478a83f4b4
Change size buffers to unsigned long int
2017-03-17 18:26:39 +01:00
DL6ER
596764e921
Simplify log routines
2017-03-14 13:44:16 +01:00
DL6ER
a859abcf60
Generate over time structure for forwarded data and discard old forwarded data on initial log parsing
2017-03-13 10:37:01 +01:00
DL6ER
f73ed48dbf
Implement FTL garbage collector
2017-03-12 21:03:05 +01:00
DL6ER
89d6567259
Add thread names
2017-03-12 16:16:36 +01:00
DL6ER
3bb6f423dc
FTL is now aware of how much memory it uses. Added ">memory" command.
2017-03-12 12:16:09 +01:00
DL6ER
fa99b5b88d
[MAJOR change] FTL is now multi-threaded. There will be one core process (which catches signals handles them), one log processing thread (waiting for log changes), one listening thread (waiting for incoming connections) and one thread for each client that is connected (waiting for requests to be answered by FTL)
2017-03-08 11:32:25 +01:00
DL6ER
77f16c83c2
Fixed error message
2017-02-13 09:23:19 +01:00
DL6ER
b01d6b6194
Interpret command line arguments (use pihole-FTL debug for debug mode)
2017-02-06 13:19:17 +01:00
DL6ER
6533043968
Create struct that holds FTL related filenames
2017-02-03 23:51:44 +01:00
DL6ER
68984e354e
Initial upload of the FTL engine
2017-02-02 12:44:45 +01:00