Re: [trinity-devel] TDE (git) crash on start - 5.8G tdm.log exhausted all disk space??

Not directly, but perhaps I'll file a bug report against the problem. Unlike the Xorg.0.log, tdm.log is never deleted and started fresh with each session. The tdm.log file just grows and grows and grows.... In my Slackware system I long ago modified the stock rc.4 startup script to include deleting the log file before actually starting run level 4, which for Slackware is the graphical login. A more appropriate solution is TDM or TDE performing its own house keeping. With that said, unless this log file has been growing for a very long time and you did not notice the ever shrinking file space, to grow to a GB size means a runaway loop of some kind. I would test methodically. That is, reboot and before starting graphical mode, ensure the log file is always deleted. If your operating system allows a spare console for command line logins even when in graphical mode (in Slackware console number 6 is excluded from graphical logins), use that console to login and monitor the tdm.log file with tail. If there is no available console, use ssh to monitor the log file. Side note: sounds as though your /var file system is on the same partition as your root file system. Placing /var on its own partition would have avoided any lock up due to file space because only that partition would have filled and not your root system. Placing /var on a separate partition is common practice and now you have real world experience why that practice started. :) Darrell