Public bug reported:

I wrote a udev rule that would not trigger when expected.  I spent 2
days working on it, trying to understand what the problem was.  I
finally figured it out -- it was a matching problem:

https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890836

The most verbose output possible is with the log level set to "debug".
This level of logging does not show users what criteria is being checked
and what the result is.  So users are working in the dark.  We have to
guess what udev is doing.  And we're bad at it, because if we could
guess correctly we probably would have written the rule correctly in the
first place.

Consider procmail.  This is an application where users write rules that
contain matching criteria.  When Procmail doesn't work as expected, the
logs show in detail what criteria matches and what does not.  This is
what udev needs.

** Affects: systemd (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1890890

Title:
  more debugging verbosity for udev rules needed

Status in systemd package in Ubuntu:
  New

Bug description:
  I wrote a udev rule that would not trigger when expected.  I spent 2
  days working on it, trying to understand what the problem was.  I
  finally figured it out -- it was a matching problem:

  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890836

  The most verbose output possible is with the log level set to "debug".
  This level of logging does not show users what criteria is being
  checked and what the result is.  So users are working in the dark.  We
  have to guess what udev is doing.  And we're bad at it, because if we
  could guess correctly we probably would have written the rule
  correctly in the first place.

  Consider procmail.  This is an application where users write rules
  that contain matching criteria.  When Procmail doesn't work as
  expected, the logs show in detail what criteria matches and what does
  not.  This is what udev needs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890890/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to