summaryrefslogtreecommitdiff
path: root/sysutils/fam/MESSAGE
diff options
context:
space:
mode:
authorjmmv <jmmv@pkgsrc.org>2004-10-17 19:20:53 +0000
committerjmmv <jmmv@pkgsrc.org>2004-10-17 19:20:53 +0000
commit665d71f19032aa7c6bdadab838c5c58b56e9aa3d (patch)
tree51577a67ccbf14a8aa45f196c661bc17568591bf /sysutils/fam/MESSAGE
parent695bd01a066f0b832a84a92640e96fb4b4dd58f5 (diff)
downloadpkgsrc-665d71f19032aa7c6bdadab838c5c58b56e9aa3d.tar.gz
Add kqueue support. This way, famd can be notified of changes to files and
directories in "real time", without having to periodically poll(2) for them after several seconds. This improves the responsiveness of applications using famd (specially GNOME) when changes to files occur from the "outside" (they are notified from changes immediately), or even from the application itself (for example, have you ever tried to rename several files from Nautilus? just a PITA). To enable kqueue, you have to pass the 'kqueue' option to the package. I'm not enabling it by default because it needs testing (but it should be enabled in a future). Furthermore, I'd like to send these patches to the FAM developers for comments too. And a review from somebody knowing kqueue could be good! (this is the first time I use the kqueue interface, so I'm not sure if everything is right). A description on how this works can be found in the files/IMonKQueue.c++ file. Note that, due to FAM's design, the easiest way to do this change is to "emulate" imon functionality. While here, add an rc.d script for famd, in case the user prefers to run it at system startup instead of from inetd (I created it while developing the kqueue functionality, so it's a good moment to add it). Adjust the MESSAGE accordingly. Bump PKGREVISION to 4.
Diffstat (limited to 'sysutils/fam/MESSAGE')
-rw-r--r--sysutils/fam/MESSAGE19
1 files changed, 11 insertions, 8 deletions
diff --git a/sysutils/fam/MESSAGE b/sysutils/fam/MESSAGE
index 07d709071cf..65120dd1c34 100644
--- a/sysutils/fam/MESSAGE
+++ b/sysutils/fam/MESSAGE
@@ -1,17 +1,20 @@
===========================================================================
-$NetBSD: MESSAGE,v 1.3 2004/03/28 22:00:04 minskim Exp $
+$NetBSD: MESSAGE,v 1.4 2004/10/17 19:20:53 jmmv Exp $
-FAM uses RPC and is usually started by the inetd(8) superserver. You need
-to enable it manually, by issuing the following steps:
-
-1) Add FAM to the system's portmapper by appending the following line to
- the /etc/rpc file:
+Because FAM uses RPC, you have to add the following line to the system's
+portmapper file (/etc/rpc):
sgi_fam 391002 fam # File Alteration Monitor
-2) Add FAM to the system's superserver by appending the following line to
- the /etc/inetd.conf file:
+After that, restart the rpcbind(8) server.
+
+Furthermore, you have to enable the FAM daemon. There are two ways to do
+this: through inetd(8) or as a standalone server. If you prefer the former
+way, add the following line to /etc/inetd.conf:
sgi_fam/1-2 stream rpc/tcp wait root ${PREFIX}/sbin/famd famd
+and reload inetd(8)'s daemon. However, if you prefer the later way, use
+the provided famd rc.d(8) script.
+
===========================================================================