any reason for the debug log in journal ?

[rienafairefr]

I was looking at boot logs (as one sometimes does 🤪 ) with journalctl on my Kubuntu desktop, and was suprised to find telltale signs of scripts with 'set -x' in it.

nov. 01 17:07:24 beehive cups.cupsd[1950]: + CUPS_PID=2272
nov. 01 17:07:24 beehive cups.cupsd[2272]: +
nov. 01 17:07:24 beehive cups.cupsd[1950]: +
nov. 01 17:07:24 beehive cups.cupsd[2272]: exec
nov. 01 17:07:24 beehive cups.cupsd[1950]: echo

I blamed myself first, I sometimes add that to scripts, even in the system, to see something better and troubleshoot. But here, I wasn't culprit in the end. I found the script that was outputting to journal was this one /snap/cups/1116/scripts/run-cupsd, and it contained the set -x, which was from the upstream package, still there :

cups-snap/scripts/run-cupsd

Line 3 in a324615

set -e -x

git blame traces to a commit of @tillkamppeter that it activates debug mode, which, yeah it does. This is "drop in a bucket", like 100 lines or so of output, but these logs probably have a better place somewhere else than the global journal, I'm just wondering what the (maybe good, no idea) rationale for adding that at that time (7 years ago)

There is a debug log file used just below in that same script, below CUPS_DEBUG_LOG=$SNAP_DATA/var/log/debug_log maybe the debug logs of the script itself could added in there, instead of the system logs.