On Di, 14.05.19 08:01, Ulrich Windl (ulrich.wi...@rz.uni-regensburg.de) wrote:

> > systemd matches these UNIX semantics closely: we output error messages
> > exactly the same way as everything else on UNIX: a brief string
> > explaining what was attempted, followed by a colon, followed by a
> > space, followed by the system error string.
> >
> > I mean, sure we can always tweak error messages more, but we generally
> > start from how C and UNIX suggest these works, and then improve from
> > there.
>
> Thanks for the explanation. Actually I'm programming in C for about 30 years
> now. The point I had tried to address was: I think it doesn't make sense to 
> use
> the low-level error code (or message) in a high level routine. Just imagine
> some find(1) command would output "No such file or directory" when no file
> matched the search criteria given. IMHO ERRNO-related messages
> should be used

I don't have to image that. It's exactly what find outputs:

    $ find /i/dont/exist
    find: ‘/i/dont/exist’: No such file or directory

Lennart

--
Lennart Poettering, Berlin
_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Reply via email to