From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kay Sievers Date: Fri, 15 Oct 2004 17:54:27 +0000 Subject: Re: Log actions releated to /etc/dev.d scripts Message-Id: <20041015175427.GA6290@vrfy.org> List-Id: References: <1097845120.5114.32.camel@homer.blizzard.org> In-Reply-To: <1097845120.5114.32.camel@homer.blizzard.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Fri, Oct 15, 2004 at 01:26:45PM -0400, Jesse Stockall wrote: > On Fri, 2004-10-15 at 13:06, Kay Sievers wrote: > > Just compile udev with "make DEBUG=true" and you will get all these in > > your syslog. We really don't want this kind of debug for normal users. > > > > Enabling debug is not a problem if you are doing development, but is a > bit of a pain for an admin or a "normal user". > > What is the rational behind having some udev actions logged, such as > what rule is used for the naming, but not others like what dev.d script > is being run? Since logging is turned off by default, this doesn't > clutter anyones logs. Maybe it is disabled on your distribution, no on mine. The logged messages are the absolute minimum. Everything else is "development debug" only. If it's really needed we may introduce a debug-level value in the config instead of the debug-switch, but that will increase the size of the udev binary. Thaks, Kay ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net Linux-hotplug-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel