El mar, 3 dic 2024 a las 17:15, Samuel Thibault (<samuel.thiba...@gnu.org>) escribió: > > Oh, that's odd indeed. Perhaps run it through rpctrace to see what > happens behind. >
I attached the rpctrace log. I'm not sure what to look for but the
following lines seem relevant:
7<--38(pid1044)->dir_lookup ("dev/zero" 65554 436) = 0 1 ""
52<--47(pid1044)
52<--47(pid1044)->file_set_size (0) = 0
52<--47(pid1044)->file_utimens ({0 0 0 0 0 0 0 0 -2 -1 -1 -1 -1 -1
-1 -1} {0 0 0 0 0 0 0 0 -1 -1 -1 -1 -1 -1 -1 -1}) = 0x40000001
(Operation not permitted)
52<--47(pid1044)->term_getctty () = 0xfffffed1 ((ipc/mig) bad
request message ID)
52<--47(pid1044)->io_stat_request () = 0 {15 0 0 0 0 0 0 0 -67 2 0
0 0 0 0 0 97 -74 1 0 0 0 0 0 -83 -90 55 103 0 0 0 0 0 0 0 0 0 0 0 0
-74 33 -128 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 -1 -1 -1 -1 -1
-1 -1 127 -77 124 55 103 0 0 0 0 0 0 0 0 0 0 0 0 -77 124 55 103 0 0 0
0 0 0 0 0 0 0 0 0 -77 124 55 103 0 0 0 0 0 0 0 0 0 0 0 0 0 32 0 0 0 0
0 0 8 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
-80 36 3 40 0 0 0 0 -8 6 0 0 0 0 0 0}
52<--47(pid1044)->term_getctty () = 0xfffffed1 ((ipc/mig) bad
request message ID)
52<--47(pid1044)->io_write_request ("Hello World!\n" -1) = 0 15
task15(pid1044)->mach_port_deallocate (pn{ 17}) = 0
trace.log
Description: Binary data
