I did some searching and found a 6.4 GB file sreenlog.0 I deleted it and then tried to nano 1 bash and it gave an error about a 1bash.swp lock file. I used VI and was able to delete the sap file and now nano works and I edited the 1 bash.
What is up with this huge screen log.0 file and how can I keep it from creating this?
Thanks
I guess you are the first to report this problem... I expect the forum to be flooded with this same issue soon.
I've been talking about this upcomming problem for a while now... the abuse of logs and recording everything while completely unnecessary.
Recording a log that will eventually fill up all the empty space just to show one line from it in the telegram message is not smart programming... pretty much all the scripts that rely on these logs will have to be rewritten to keep the logs under control.
Devs, if you realy need that log, create a ramdisk (tmpfs) and record screenlog (or whatever other log you need) there and create a cronjob to periodicaly clean it. There's really nothing important from screenlog that needs to be permanently recorded so a, lets say 100 MB ramdisk is perfect solution. Direct the logs there, extract whatever you need when the script is run, then flush the log. Shouldn't be very difficult to do
I heard you mate and started to changing my codes to use named pipes , cant give any ETA, but will do my best to get them ready for next version.