Path: ...!news.roellig-ltd.de!open-news-network.org!weretis.net!feeder8.news.weretis.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: "Carlos E.R." Newsgroups: comp.os.linux.misc Subject: Re: What programs do you make sure are installed on a new Linux Date: Tue, 19 Nov 2024 08:57:00 +0100 Lines: 24 Message-ID: References: <8db593ab-0793-2b31-ebc3-922a5d2fc241@example.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net 98al1TJK9Ri1s4w8RdQrqwTZJ1sJtJBAOXe4WmS9oWHje+qj6R X-Orig-Path: Telcontar.valinor!not-for-mail Cancel-Lock: sha1:jQ7LZ25Q6ZLCSog+uuPOJQ2Ksl0= sha256:WxMMPAbB5vaDZhR62fpK3QYQhAykRt4I2s+8T7madTk= User-Agent: Mozilla Thunderbird Content-Language: es-ES, en-CA In-Reply-To: Bytes: 2357 On 2024-11-17 19:07, rbowman wrote: > On Sun, 17 Nov 2024 17:17:37 GMT, Charlie Gibbs wrote: > >> Horses for courses. Never underestimate the value of a few printf()s >> sprinkled here and there (or log file writes if you're really headless). >> I'm still a fan of makefiles. > > I'm a dinosaur so my preferred technique is either printf or log files. > For production code I've sometimes created a sequence of log statements > that can be turned on with a flag that are a narrative of what's going on. > My goal is a support person can read the file and see where the problem > occurs. Often it is a configuration issue they can fix. > > The nice part is the technique can be used with any language and is > effective where a debugger isn't available. The other day a daemon program spewed 2 gigabytes of log entries, all almost identical (the filename changed). The program was tracker-extract. Currently there are many programs that spew chat like there is no tomorrow to syslog :-/ -- Cheers, Carlos.