Reaction score: 1
I was following an example found in: Practical rc.d scripting in BSD - at https://docs.freebsd.org/en/articles/rc-scripting/ ...and the 1st example, shows the "dummy" script. So, I reproduced the script in /etc/rc.conf.d, then I corrected errors, set the execute bit, and made a run. # start dummy failed with not a command. Then, I found a SirDice comment mentioning the full path. So, I tried: # /bin/sh /etc/rc.conf.d/dummy start - now it ran correctly, displaying a simple output message: Nothing Done. Afterwards, I was copying a file or two, nothing else, and I decided to run dummy again. # /bin/sh /etc/rc.conf.d/dummy start - but, after waiting for 30 seconds, came this response: Segmentation fault (core dumped). So, I rebooted but receive the same result. I have another basic shell program called myback and, when started, I receive the same segmentation fault message. I don’t really know how to identify the cause, I can't find (or understand) the .core dump file. I understand that the .core dump is Core Dump/Segmentation fault is a specific kind of error caused by accessing memory that “does not belong to you.” I have lately been experimenting with running transmission from the command line and also in KDE5. I receive a notification that terminal failed to acquire buffer space, but even then, the program did not crash or produce a segmentation error. I ran pkg delete transmission, but I still see the system attempting to redirect ports, so I know it's not completely gone. Any suggestions? PS this is a test system and I don't mind reloading F-BSD13 from scratch. Does anyone know more about getting a Segmentation fault after creating a few shell scripts?