setting distinct core file names

[Conrad Meyer]

One (ugly) trick is to use multiple filesystem links to the script
interpreter, where the link names distinguish the scripts.  E.g.,

$ ln /bin/sh /libexec/my_script_one_sh
$ ln /bin/sh /libexec/my_script_two_sh
$ cat myscript1.sh
#!/libexec/my_script_one_sh
...

Cores will be dumped with %N of "my_script_one_sh."

Best,
Conrad
On Tue, Nov 27, 2018 at 9:29 AM Willem Jan Withagen <wjw at digiware.nl> wrote:
>
> Hi,
>
> Looking at core(5) and sysctl it looks like these are system wide
> settings....
>
> Is there a possibility that a program can set its own corefile name (and
> path?)
>
> During parallel testing I'm running into these scripts that generate
> cores, but they end up all in the same location. But it would be nice if
> I could one way or another determine which file came from what script.
>
> But for that I would need to be able to set something like
>         %N."script".core
> as the core name. I could then put that in then ENV of the script and
> the program would pick it up and set its own corefile name.
>
> Possible??
> --WjW
> _______________________________________________
> freebsd-hackers at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe at freebsd.org"