d/freebsd-skq
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
212,051 Commits 4 Branches 49 Tags 2 GiB
c11e6697ea
Commit Graph

15 Commits

Author SHA1 Message Date
pjd
c5fe5a76f2 For functions that return -1 on failure check exactly for -1 and not for 
any negative number.

MFC after:	3 days
 2012-01-10 22:39:07 +00:00
pjd
2c59e5d543 Use PJDLOG_ASSERT() and PJDLOG_ABORT() everywhere instead of assert(). 
MFC after:	3 days
 2011-09-27 08:50:37 +00:00
pjd
d3221d1a45 Increase debug level of "Checking hooks." message. 
MFC after:	1 week
 2011-03-21 14:53:27 +00:00
pjd
ee6f63ce17 Log when we start hooks checking and when we execute a hook. 
MFC after:	1 week
 2011-03-21 08:38:24 +00:00
pjd
e06bfb0a1b Use snprlcat() instead of two strlcat(3)s. 
MFC after:	1 week
 2011-03-21 08:37:50 +00:00
pjd
18d56b43fe 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
 2011-01-12 16:16:54 +00:00
pjd
b905920a72 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
 2011-01-12 14:38:17 +00:00
pjd
ff47d7260c Use closefrom(2) instead of close(2) in a loop. 
MFC after:	1 week
 2010-10-20 21:10:01 +00:00
pjd
884d1009d2 Clear signal mask before executing a hook. 
Submitted by:	Mikolaj Golub <to.my.trociny@gmail.com>
MFC after:	3 days
 2010-10-16 22:48:48 +00:00
pjd
b85b0868d9 hook_check() is now only used to report about long-running hooks, so the 
argument is redundant, remove it.

MFC after:	3 days
 2010-10-04 21:43:06 +00:00
pjd
22936fe435 Plug memory leak on fork(2) failure. 
Submitted by:	Mikolaj Golub <to.my.trociny@gmail.com>
MFC after:	3 days
 2010-09-26 10:39:01 +00:00
pjd
9a66bc9a30 - 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
 2010-08-29 21:39:49 +00:00
pjd
aeab5efe07 - 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
 2010-08-27 14:38:12 +00:00
pjd
dd3961e615 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
 2010-08-27 14:35:39 +00:00
pjd
1c1e2e8b71 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
 2010-02-18 23:16:19 +00:00