A non-debug core file can still be very useful and yes, there a various ways to
instruct your system to allow core files to be created. Detailed here: >http://wiki.synchro.net/howto:gdb#core_file
Moving and renaming this, since it is no longer about TW or JS.
A non-debug core file can still be very useful and yes, there a various ways to
instruct your system to allow core files to be created. Detailed here: >http://wiki.synchro.net/howto:gdb#core_file
$ulimit -c
unlimited
/etc/sysctl.conf has the following two lines:
kernel.core_uses_pid = 1
kernel.core_pattern = /tmp/core.%e.%p
I get the segfault and check /tmp. Nothing there.
So, what package is it that a developer would have on their *nix box that probably doesn't come with a debian stable install that I need to install
to get core files?
Or maybe a more pertinent question... since sbbs has to be started with
sudo in order to bind to port 23, how does one allow superuser to create core files? When I su to root, I get this:
$ulimit -c
0
Moving and renaming this, since it is no longer about TW or JS.
A non-debug core file can still be very useful and yes, there a various ways to
instruct your system to allow core files to be created. Detailed here: >>http://wiki.synchro.net/howto:gdb#core_file
$ulimit -c
unlimited
/etc/sysctl.conf has the following two lines:
kernel.core_uses_pid = 1
kernel.core_pattern = /tmp/core.%e.%p
I get the segfault and check /tmp. Nothing there.
So, what package is it that a developer would have on their *nix box that >probably doesn't come with a debian stable install that I need to install
to get core files?
Or maybe a more pertinent question... since sbbs has to be started with
sudo in order to bind to port 23, how does one allow superuser to create
core files? When I su to root, I get this:
$ulimit -c
0
Which could be why sbbs does not create a core file... I don't think it is >getting far enough to change the user back and, even if it were, I don't
know that it would matter.
If you're running sbbs as a service, then your service startup file (e.g. sbbs.service or init.d/sbbs file) may need the core limit adjusted there. There's a instructions on the gdb wiki page about that.
Or maybe a more pertinent question... since sbbs has to be started with sudo in order to bind to port 23, how does one allow superuser to create core files? When I su to root, I get this:
$ulimit -cYou could put "ulimit -c unlimited" in your /root/.profile, but I don't think >that's going to fix the problem (but you could try), unless you're running sbbs
0
manually from a login shell as root.
Do ;SHELL in your bbs then ulimit -a
You'll probably find it starts up without ulimit set.
Are you using init.d or systemd to startup? There's hints on the wiki
for what to put in the systemd startup script to set ulimit.
Do ;SHELL in your bbs then ulimit -a
You'll probably find it starts up without ulimit set.
If it was actually running, and not failing to start because of a segmentation fault, that might work. :) As it is, I cannot do anything in the bbs.
Are you using init.d or systemd to startup? There's hints on the wiki
for what to put in the systemd startup script to set ulimit.
There are hints, and I followed the ones for getting a core dumps if you
are not starting the system as a service. They did not work and I suspect it is because I have to start the bbs by using sudo to run the script. Otherwise, the ports will not bind.
P.S. I did confirm that my bbs user is correctly configured to create core files otherwise, ironically when scfg crashed. As I don't have to start it with sudo, it did create one, although I do not appear to have any program installed which is able to open it in any legible format.
Do ;SHELL in your bbs then ulimit -a
You'll probably find it starts up without ulimit set.
If it was actually running, and not failing to start because of a segmentation fault, that might work. :) As it is, I cannot do anything in the bbs.
Are you using init.d or systemd to startup? There's hints on the wiki
for what to put in the systemd startup script to set ulimit.
There are hints, and I followed the ones for getting a core dumps if you
are not starting the system as a service. They did not work and I suspect it is because I have to start the bbs by using sudo to run the script. Otherwise, the ports will not bind.
If you're running sbbs as a service, then your service startup file (e.g.
sbbs.service or init.d/sbbs file) may need the core limit adjusted there.
There's a instructions on the gdb wiki page about that.
I am not running it as a service. I am running it in console, from a shell >script that I envoke with sudo.
Or maybe a more pertinent question... since sbbs has to be started with >> > sudo in order to bind to port 23, how does one allow superuser to create >> > core files? When I su to root, I get this:You could put "ulimit -c unlimited" in your /root/.profile, but I don't think >>that's going to fix the problem (but you could try), unless you're running sbbs
$ulimit -c
0
manually from a login shell as root.
You are correct, it does not fix it.
It sounds sort of like someone running it in console, who has to use sudo to >bind port 23, will never get a core file produced. If that is the case, what >do they do when they get a segmentation fault?
P.S. I did confirm that my bbs user is correctly configured to createcore
files otherwise, ironically when scfg crashed. As I don't have to startit
with sudo, it did create one, although I do not appear to have any program installed which is able to open it in any legible format.
No, you do not. If you install Synchronet as service with the instructions here:
http://wiki.synchro.net/install:nix#daemon_mode
or here:
http://wiki.synchro.net/howto:systemd
(depending on your distro)
... you will not need to use "sudo" for anything.
What's your limits.conf file look like?
I ran "man limits.conf" and it contained this possibly helpful note:
NOTE: group and wildcard limits are not applied to the root user. To set a
limit for the root user, this field must contain the literal username root.
What's your limits.conf file look like?
I ran "man limits.conf" and it contained this possibly helpful note:
NOTE: group and wildcard limits are not applied to the root user. To set a
limit for the root user, this field must contain the literal username root.
Ahhhh, I should have looked there! :)
As you know now, I ran it without sudo to get a core file. gdb was already installed, so you should have some output in your email box. Thanks!
No, you do not. If you install Synchronet as service with the instructions here:
http://wiki.synchro.net/install:nix#daemon_mode
or here:
http://wiki.synchro.net/howto:systemd
(depending on your distro)
... you will not need to use "sudo" for anything.
I tried it as a service and did not like it. It was a long time ago, but I am thinking I could not get it to work. So, yes, if I want to run it in a console (I do), I have to run it using sudo.
Sysop: | MCMLXXIX |
---|---|
Location: | Prospect, CT |
Users: | 325 |
Nodes: | 10 (0 / 10) |
Uptime: | 04:50:35 |
Calls: | 510 |
Messages: | 220570 |