diff --git a/devdocs/todo.txt b/devdocs/todo.txt
index e79ad5c8..38b822cd 100644
--- a/devdocs/todo.txt
+++ b/devdocs/todo.txt
@@ -8,19 +8,26 @@ Problem:
 	AyaNova log and system journal eating up all disk space due to postgres being down for unknown reason and ayanova repeatedly trying to do stuff in this condition and then issuing errors and LOGGING
 
 potential fixes: TODO HERE:
-	Detect postgres is unreachable and stop digging a hole, wait to resolve it before continuing on again
-
-	Don't log same message repeatedly
-		actually this is not necessary if just stop running jobs when can't reach sql server
+	FIXED Detect postgres is unreachable and stop digging a hole, wait to resolve it before continuing on again
 	FIXED don't dual log to system journal logs and ayanova log
 		Ayanova is not only logging but also directing it's output to the terminal window which in linux system service is being logged also to the journal logs
 		AyaNova should only ouput to it's log file, not to terminal with the sole exception of the initial boot up period
 		This may be a configuration in the logging library set this way??
-	cap system journal logs in linux
+	TODO: Add this to the standard server config script
+		cap system journal logs in linux to 250mb or some reasonable value
 		https://linuxhandbook.com/clear-systemd-journal-logs/
-	cap ayanova logs in configuration
-	If detect db is unavailable then log that and stop job processor etc basically freeze the server jobs until the db becomes available
+	TODO: cap ayanova logs in configuration
+		something in here, but maybe it's config is different compare with code for logrotate in use now and see what the exact settings are
+		https://github.com/NLog/NLog/wiki/Configuration-file
+		https://github.com/NLog/NLog/wiki/File-target#archival-options
+		https://nlog-project.org/config/
+		NOTE: it may make sense to swtich from rotating every week to rotating on size instead, after all why force to rotate a nearly empty log?
+
+
+
+	DONE: If detect db is unavailable then log that and stop job processor etc basically freeze the server jobs until the db becomes available
 		server state db unavailble not just at boot but during ops
+		
 quick fixes:
 https://support.hostway.com/hc/en-us/articles/360001972270-How-to-clean-log-files-in-Linux
 https://linuxhandbook.com/clear-systemd-journal-logs/