Ludovic Courtès <l...@gnu.org> writes:
>> ;;; (ACTUAL ((service (version 0) (provides (root shepherd))
>> (requires ()) (respawn? #f) (docstring "The root service is used to
>> operate on shepherd itself.") (enabled? #t) (running (process
>> (version 0) (id 14089) (command
>> ("/gnu/store/mwv03cfpqwvnffq76fp4x1kmn6833dpa-guile-3.0.9/bin/guile"
>> "--no-auto-compile"
>> "/tmp/guix-build-shepherd-1.0.2.drv-0/shepherd-1.0.2/shepherd" "-I"
>> "-s" "t-socket-14001" "-c" "t-conf-14001" "-l" "t-log-14001"
>> "--pid=t-pid-14001"))))
>
> This is actually built through transparent emulation, not on a native
> AArch64 machine, and that shows in the discrepancy above:
> /proc/PID/cmdline lets ‘qemu-aarch64’ through, whereas
> /proc/self/cmdline (as used by ‘process-command’ in the Shepherd) hides
> it.
True. I do have the qemu service for aarch64-linux enabled. In the
deployment file I declare (build-locally? #true), but I will never not
be confused about what "locally" means in this context :)
--
Ricardo
