| #
256281 |
|
10-Oct-2013 |
gjb |
Copy head (r256279) to stable/10 as part of the 10.0-RELEASE cycle.
Approved by: re (implicit)
Sponsored by: The FreeBSD Foundation |
| #
229945 |
|
10-Jan-2012 |
pjd |
For functions that return -1 on failure check exactly for -1 and not for
any negative number.
MFC after: 3 days
|
| #
225787 |
|
27-Sep-2011 |
pjd |
Use PJDLOG_ASSERT() and PJDLOG_ABORT() everywhere instead of assert().
MFC after: 3 days
|
| #
219832 |
|
21-Mar-2011 |
pjd |
Increase debug level of "Checking hooks." message.
MFC after: 1 week
|
| #
219817 |
|
21-Mar-2011 |
pjd |
Log when we start hooks checking and when we execute a hook.
MFC after: 1 week
|
| #
219816 |
|
21-Mar-2011 |
pjd |
Use snprlcat() instead of two strlcat(3)s.
MFC after: 1 week
|
| #
217312 |
|
12-Jan-2011 |
pjd |
execve(2), not fork(2) resets signal handler to the default value (if it isn't
ignored). Correct comment talking about that.
Pointed out by: kib
MFC after: 3 days
|
| #
217308 |
|
12-Jan-2011 |
pjd |
Add a note that when custom signal handler is installed for a signal,
signal action is restored to default in child after fork(2).
In this case there is no need to do anything with dummy SIGCHLD handler,
because after fork(2) it will be automatically reverted to SIG_IGN.
Obtained from: Wheel Systems Sp. z o.o. http://www.wheelsystems.com
MFC after: 3 days
|
| #
214119 |
|
20-Oct-2010 |
pjd |
Use closefrom(2) instead of close(2) in a loop.
MFC after: 1 week
|
| #
213938 |
|
16-Oct-2010 |
pjd |
Clear signal mask before executing a hook.
Submitted by: Mikolaj Golub <to.my.trociny@gmail.com>
MFC after: 3 days
|
| #
213429 |
|
04-Oct-2010 |
pjd |
hook_check() is now only used to report about long-running hooks, so the
argument is redundant, remove it.
MFC after: 3 days
|
| #
213183 |
|
26-Sep-2010 |
pjd |
Plug memory leak on fork(2) failure.
Submitted by: Mikolaj Golub <to.my.trociny@gmail.com>
MFC after: 3 days
|
| #
211976 |
|
29-Aug-2010 |
pjd |
- Add hook_fini() which should be called after fork() from the main hastd
process, once it start to use hooks.
- Add hook_check_one() in case the caller expects different child processes
and once it can recognize it, it will pass pid and status to hook_check_one().
MFC after: 2 weeks
Obtained from: Wheel Systems Sp. z o.o. http://www.wheelsystems.com
|
| #
211885 |
|
27-Aug-2010 |
pjd |
- Run hooks in background - don't block waiting for them to finish.
- Keep all hooks we're running in a global list, so we can report when
they finish and also report when they are running for too long.
MFC after: 2 weeks
Obtained from: Wheel Systems Sp. z o.o. http://www.wheelsystems.com
|
| #
211884 |
|
27-Aug-2010 |
pjd |
When logging to stdout/stderr don't close those descriptors after fork().
MFC after: 2 weeks
Obtained from: Wheel Systems Sp. z o.o. http://www.wheelsystems.com
|
| #
204076 |
|
18-Feb-2010 |
pjd |
Please welcome HAST - Highly Avalable Storage.
HAST allows to transparently store data on two physically separated machines
connected over the TCP/IP network. HAST works in Primary-Secondary
(Master-Backup, Master-Slave) configuration, which means that only one of the
cluster nodes can be active at any given time. Only Primary node is able to
handle I/O requests to HAST-managed devices. Currently HAST is limited to two
cluster nodes in total.
HAST operates on block level - it provides disk-like devices in /dev/hast/
directory for use by file systems and/or applications. Working on block level
makes it transparent for file systems and applications. There in no difference
between using HAST-provided device and raw disk, partition, etc. All of them
are just regular GEOM providers in FreeBSD.
For more information please consult hastd(8), hastctl(8) and hast.conf(5)
manual pages, as well as http://wiki.FreeBSD.org/HAST.
Sponsored by: FreeBSD Foundation
Sponsored by: OMCnet Internet Service GmbH
Sponsored by: TransIP BV
|