History log of /freebsd/usr.sbin/watchdogd/watchdogd.c (Results 51 – 75 of 91)
Revision (<<< Hide revision tags) (Show revision tags >>>) Date Author Comments
# 193e2b55 30-Aug-2012 Andrey Zonov <zont@FreeBSD.org>

- It's also need to lock current memory.

Approved by: kib (mentor)
MFC after: 1 week


# e489ac6c 28-Aug-2012 Andrey Zonov <zont@FreeBSD.org>

- Don't allow watchdogd(8) to be swapped out.
On machines with huge amount of swap and high IO activity,
watchdogd(8) may wait for a swap memory longer than timeout and
sometimes fires.

Approv

- Don't allow watchdogd(8) to be swapped out.
On machines with huge amount of swap and high IO activity,
watchdogd(8) may wait for a swap memory longer than timeout and
sometimes fires.

Approved by: kib (mentor)
MFC after: 1 week

show more ...


Revision tags: release/8.3.0_cvs, release/8.3.0, release/9.0.0, release/7.4.0_cvs, release/8.2.0_cvs, release/7.4.0, release/8.2.0
# f145c771 26-Sep-2010 Ed Maste <emaste@FreeBSD.org>

Protect the watchdog daemon against swap OOM killer. This is similar to
SVN r199804 which added protection to sshd, cron, syslogd, and inetd.


# d10d35b3 20-Jul-2010 Xin LI <delphij@FreeBSD.org>

Staticify local variables.

While I'm there also add a 'static' keyword for a function to make it
consistent with prototype.

Reviewed by: phk
MFC after: 3 months


Revision tags: release/8.1.0_cvs, release/8.1.0, release/7.3.0_cvs, release/7.3.0
# 1a0fda2b 04-Mar-2010 Dag-Erling Smørgrav <des@FreeBSD.org>

IFH@204581


# 9199c09a 06-Jan-2010 Warner Losh <imp@FreeBSD.org>

Merge from head at r201628.

# This hasn't been tested, and there are at least three bad commits
# that need to be backed out before the branch will be stable again.


# 10bc3a7f 29-Dec-2009 Ed Schouten <ed@FreeBSD.org>

ANSIfy almost all applications that use WARNS=6.

I was considering committing all these patches one by one, but as
discussed with brooks@, there is no need to do this. If we ever
need/want to merge

ANSIfy almost all applications that use WARNS=6.

I was considering committing all these patches one by one, but as
discussed with brooks@, there is no need to do this. If we ever
need/want to merge these changes back, it is still possible to do this
per application.

show more ...


# c409ce41 21-Dec-2009 Ruslan Ermilov <ru@FreeBSD.org>

Don't hide an error if the initial attempt to program a watchdog from
within watchdogd(8) fails. This is also consistent with watchdog(8).


Revision tags: release/8.0.0_cvs, release/8.0.0, release/7.2.0_cvs, release/7.2.0, release/7.1.0_cvs, release/7.1.0, release/6.4.0_cvs, release/6.4.0, release/7.0.0_cvs, release/7.0.0, release/6.3.0_cvs, release/6.3.0, release/6.2.0_cvs, release/6.2.0
# 0f71a1cb 15-Dec-2006 Nick Hibma <n_hibma@FreeBSD.org>

Don't exit from watchdogd on receiving a signal if we cannot stop the watchdog.
That'll require -KILL. This avoids resetting your system on one of the
watchdogs that you cannot disable.


Revision tags: release/5.5.0_cvs, release/5.5.0, release/6.1.0_cvs, release/6.1.0
# 5c272530 06-Mar-2006 Poul-Henning Kamp <phk@FreeBSD.org>

Fix usage().

Submitted by: Adrian Steinmann <ast@marabu.ch>


Revision tags: release/6.0.0_cvs, release/6.0.0
# 2a5f59b2 30-Sep-2005 Poul-Henning Kamp <phk@FreeBSD.org>

Report any errors we might see when disabling the watchdog.

Complain about extra arguments so people don't get surprised
if they type "watchdog 0"


# 8b28aef2 16-Sep-2005 Pawel Jakub Dawidek <pjd@FreeBSD.org>

Pidfiles should be created with permission preventing users from opening
them for reading. When user can open file for reading, he can also
flock(2) it, which can lead to confusions.

Pointed out by:

Pidfiles should be created with permission preventing users from opening
them for reading. When user can open file for reading, he can also
flock(2) it, which can lead to confusions.

Pointed out by: green

show more ...


# 0ea90af0 24-Aug-2005 Pawel Jakub Dawidek <pjd@FreeBSD.org>

Use pidfile(3) in watchdogd(8).


Revision tags: release/5.4.0_cvs, release/5.4.0
# bdd466ff 19-Mar-2005 Marius Strobl <marius@FreeBSD.org>

When disarming a watchdog by using an interval of WD_TO_NEVER a non-zero
return value of the ioctl doesn't indicate that the command has failed
so don't let watchdog(8) return an error in this case.

When disarming a watchdog by using an interval of WD_TO_NEVER a non-zero
return value of the ioctl doesn't indicate that the command has failed
so don't let watchdog(8) return an error in this case.

MFC after: 3 days

show more ...


Revision tags: release/4.11.0_cvs, release/4.11.0, release/5.3.0_cvs, release/5.3.0
# a693939e 29-Jul-2004 Brian Feldman <green@FreeBSD.org>

Disable memory locking that could keep watchdogd from deadlocking itself
if the swap subsystem failed.

Requested by: phk


# 5e60838b 23-Jul-2004 Brian Feldman <green@FreeBSD.org>

Now that mlockall(2) is unbroken, use it to keep watchdogd(8) permanently
out of swap.


Revision tags: release/4.10.0_cvs, release/4.10.0
# 670c8a8c 03-May-2004 Sean Kelly <smkelly@FreeBSD.org>

Bump the copyright year since I forgot last time.


# 459336c4 28-Apr-2004 Sean Kelly <smkelly@FreeBSD.org>

Update comments to reflect changes made by phk. Also no longer need
<sys/sysctl.h>.


# 4103b765 28-Feb-2004 Poul-Henning Kamp <phk@FreeBSD.org>

Rename the WATCHDOG option to SW_WATCHDOG and make it use the
generic watchdoc(9) interface.

Make watchdogd(8) perform as watchdog(8) as well, and make it
possible to specify a check command to run,

Rename the WATCHDOG option to SW_WATCHDOG and make it use the
generic watchdoc(9) interface.

Make watchdogd(8) perform as watchdog(8) as well, and make it
possible to specify a check command to run, timeout and sleep
periods.

Update watchdog(4) to talk about the generic interface and add
new watchdog(8) page.

show more ...


Revision tags: release/5.2.1_cvs, release/5.2.1, release/5.2.0_cvs, release/5.2.0, release/4.9.0_cvs, release/4.9.0
# bc8b0878 03-Jul-2003 Sean Kelly <smkelly@FreeBSD.org>

o style(9) fixes
- Reordered #includes
- Only include <sys/types.h>, not it and <sys/cdefs.h>
o style.Makefile(5) fixes
- No SRCS= line when only one src file with same name as program
o Use wa

o style(9) fixes
- Reordered #includes
- Only include <sys/types.h>, not it and <sys/cdefs.h>
o style.Makefile(5) fixes
- No SRCS= line when only one src file with same name as program
o Use warn()/errx() instead of fprintf()
- Integrated patch from Philippe Charnier <charnier@xp11.frmug.org>

Approved by: jeff (mentor)

show more ...


# 055d177f 26-Jun-2003 Sean Kelly <smkelly@FreeBSD.org>

Unbreak this for alpha and friends.

Double pointy hat to me, or something.


# e931de40 26-Jun-2003 Maxim Konovalov <maxim@FreeBSD.org>

o Fix typo.

Submitted by: smkelly


# 370c3cb5 26-Jun-2003 Sean Kelly <smkelly@FreeBSD.org>

- Add a software watchdog facility.

This commit has two pieces. One half is the watchdog kernel code which lives
primarily in hardclock() in sys/kern/kern_clock.c. The other half is a userland
daemo

- Add a software watchdog facility.

This commit has two pieces. One half is the watchdog kernel code which lives
primarily in hardclock() in sys/kern/kern_clock.c. The other half is a userland
daemon which, when run, will keep the watchdog from firing while the userland
is intact and functioning.

Approved by: jeff (mentor)

show more ...


# 9199c09a 06-Jan-2010 Warner Losh <imp@FreeBSD.org>

Merge from head at r201628.

# This hasn't been tested, and there are at least three bad commits
# that need to be backed out before the branch will be stable again.


# 10bc3a7f 29-Dec-2009 Ed Schouten <ed@FreeBSD.org>

ANSIfy almost all applications that use WARNS=6.

I was considering committing all these patches one by one, but as
discussed with brooks@, there is no need to do this. If we ever
need/want to merge

ANSIfy almost all applications that use WARNS=6.

I was considering committing all these patches one by one, but as
discussed with brooks@, there is no need to do this. If we ever
need/want to merge these changes back, it is still possible to do this
per application.

show more ...


1234