Date: Fri, 02 Aug 2019 13:46:56 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 239144] Identify generic RC framework extensions to improve ports script debugging Message-ID: <bug-239144-7788-6vgbGhvdaq@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-239144-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-239144-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D239144 Greg Veldman <freebsd@gregv.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |freebsd@gregv.net --- Comment #7 from Greg Veldman <freebsd@gregv.net> --- Some daemons can be quite verbose, and can be so long after startup. Makin= g a global change to redirect all that to syslog is actually a fairly significa= nt functionality change, especially on small/embedded systems where the admin might not want all that extra info. Maybe I'm being overly simplistic, but if you're having a problem with daem= on startup, why not just look in the rc script, see what it's doing, then do t= hat manually from your terminal with whatever levels of debug/verbosity/output redirection you find most appropriate? The primary function of the rc framework is to be an automation tool, not a debugging tool, IMHO. Which i= sn't to say making debugging easier is a bad thing, but rather if something like this is implemented on a large scale the defaults should probably reflect t= he current behavior, with the option for the local admin to change if desired. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-239144-7788-6vgbGhvdaq>