https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=186114
--- Comment #33 from Eugene Grosbein ---
(In reply to Cassiano Peixoto from comment #32)
I'd better say "corefile" instead of "crashdump" as crashdump is generated for
kernel panic and core file for userland process crashed or killed with
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=186114
--- Comment #34 from Cassiano Peixoto ---
(In reply to Eugene Grosbein from comment #33)
I tried like you said, but didn't work, look:
# sysctl kern.corefile='/var/tmp/%N.core'
# ps ax | grep mpd5
31784 - Ss 0:00.01 /usr/local/sbin
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=186114
--- Comment #35 from Eugene Grosbein ---
(In reply to Cassiano Peixoto from comment #34)
Does "killall" really terminate the process or does it continue to run?
Perhaps, the signal is blocked for some reason. There are several ways to star
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=186114
--- Comment #36 from Cassiano Peixoto ---
(In reply to Eugene Grosbein from comment #35)
it's not running anymore, look:
# ps ax | grep mpd5
52264 1 S+ 0:00.00 grep mpd5
# /usr/local/etc/rc.d/mpd5 forcestart
Starting mpd5.
# ps ax
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=186114
--- Comment #37 from Eugene Grosbein ---
(In reply to Cassiano Peixoto from comment #36)
Do you use tcsh for your login shell?
Anyway, try starting mpd using direct command "/usr/local/sbin/mpd5 -p
/var/run/mpd5.pid -b" for a test instead
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=186114
--- Comment #38 from Cassiano Peixoto ---
(In reply to Eugene Grosbein from comment #37)
Same behaviour:
# ps ax | grep mpd5
53396 1 R+ 0:00.00 grep mpd5
# /usr/local/sbin/mpd5 -p /var/run/mpd5.pid -b
# ps ax | grep mpd5
53402 -
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=186114
--- Comment #39 from Eugene Grosbein ---
(In reply to Cassiano Peixoto from comment #38)
Please show output of the command: dmesg | grep mpd5
--
You are receiving this mail because:
You are on the CC list for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=186114
--- Comment #40 from Cassiano Peixoto ---
(In reply to Eugene Grosbein from comment #39)
# dmesg | grep mpd5
pid 53402 (mpd5), uid 0: exited on signal 3
pid 53441 (mpd5), uid 0: exited on signal 3
pid 53758 (mpd5), uid 0: exited on signal
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=186114
--- Comment #41 from Eugene Grosbein ---
(In reply to Cassiano Peixoto from comment #40)
The signal is delivered but core generation is disabled for some reason. To
find it, please show output of commands:
sysctl kern.coredump
proccontrol
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=186114
--- Comment #42 from Cassiano Peixoto ---
(In reply to Eugene Grosbein from comment #41)
I've just found out. My coredumpsize limit has been configured to 0Kb :(
Now it worked fine. Thanks for your help. I'll keep you posted. Until now it'
On Mon, 2017-06-12 at 13:19 +0200, Tijl Coosemans wrote:
> On Sun, 11 Jun 2017 22:13:14 + "Bjoern A. Zeeb" s.zabbadoz.net> wrote:
> > On 11 Jun 2017, at 19:59, Tijl Coosemans wrote:
> > > I recently got a new modem/router from my ISP that supports
> > > IPv6. Added
> > > ifconfig_em0_ipv6="in
In article <1497408664.2220.3.ca...@me.com>, rpa...@me.com writes:
>I don't see any reason why we shouldn't have privacy addresses enabled
>by default. In fact, back in 2008 no one voiced their concerns.
Back in 2008 most people hadn't had their networks fall over as a
result of MLD listener rep
On Tue, 2017-06-13 at 22:57 -0400, Garrett Wollman wrote:
> In article <1497408664.2220.3.ca...@me.com>, rpa...@me.com writes:
>
> > I don't see any reason why we shouldn't have privacy addresses
> > enabled
> > by default. In fact, back in 2008 no one voiced their concerns.
>
> Back in 2008 mos
13 matches
Mail list logo
