Hi K Gopal, That's a good report.
K Gopal Krishna <[email protected]> writes: > Here is the data after testing: > > Services: > Tested: 76 > Excluded: All LSB scripts and systemd components such as networkd, > volatile-root, etc > Successfully starting: 34 > Ratio: 0.447 > > Common failure patterns: > [...] > > - Failure to start because of special start / stop functionality. What does "special start" mean? Could you show an example? > [...] > > Sockets: > Tested: 15 > Excluded: 0 > Working: 0 > Ratio: 0 > > Failure patterns: > > Currently all socket units under Debian's `/lib/systemd/system` directory > rely > on a filesystem socket which xinetd doesn't support. xinetd works over TCP / > UDP. Further work is needed. Please replace xinetd with socket-activate and try again: https://packages.qa.debian.org/s/socket-activate.html > Timers: > Tested: 7 > Working: 3 > Ratio: 0.428 > > Failure patterns: > > - Currently the translator handles Calendar special expression as described > here: https://www.freedesktop.org/software/systemd/man/systemd.time.html > > - The four failed translations are because of the units following a format > not > handled by the translator such as: Thu,Fri 2012-*-1,5 11:12:13 or > OnBootSec=15min. OK. Cheers, Benda
