Out signal(3) man page screams at the reader with emphasis:
Unlike previous signal facilities, the handler func() remains
installed after a signal has been delivered.
This paragraph and its supposed importance is probably a bit opaque
for a modern reader. It has not been relevant in ... 35
> So that it can atomically overwrite the destination using rename(2).
OK, I thought something like that.
But the destination dir didn't exist and was created by pax itself.
> File a PR.
bin/59547.
In article ,
Edgar Fuß wrote:
>I tried to copy a tree with pax -wr -pe that included a 256-byte filename.
>I got an error
> pax: cannot create /.//.mInz1u
>(File name too long)
>Why does pax try to create the destination with a random-looking suffix?
So that it can atomically overwrite the
I tried to copy a tree with pax -wr -pe that included a 256-byte filename.
I got an error
pax: cannot create /.//.mInz1u
(File name too long)
Why does pax try to create the destination with a random-looking suffix?
