On 19-05-2010 23:56, Sam Varshavchik wrote: > Emerson Pinter writes: > >> I'm using Courier-IMAP 4.4.0 in my servers. Now I'm installing a new >> server, and if I use CourierIMAP 4.7.0, the user gets this [ALERT] when >> authenticates: >> Filesystem notification initialization error -- contact your mail >> administrator (check for configuration errors with the FAM/Gamin >> library) >> >> >> I don't want to use IMAP IDLE with Courier IMAP, I have to remove this >> alert from source code if I want to use courier 4.7 without IDLE ? > > You'll have to rebuild Courier without FAM support. This is done by > uninstalling FAM completely before building Courier. >
This is bad coding practice. The list of libraries available on the build computer is generally unrelated to the list of libraries on the runtime computer, unless they happen to be the same chroot of the same machine and the machine is never reconfigured after your program was compiled. This is why the whole ./configure, GNU autotools etc. approach sucks. One example is a correctly compiled .rpm package. Such a package would have been compiled either with or without FAM present and if courier-imap assumes that to definitely indicate if the target machine will have FAM installed, two nearly identical .rpm packages will need to be built (one with FAM dependency, one without FAM support at all). > I don't know why people are having these issues with FAM. I've never > experienced any sort of issues with FAM, on any one of my machines, > even though one of them was initially Red Hat 4 (not Fedora 4, Red Hat > 4), and has been upgraded over the years to the now-uptodate Fedora > 12. For me, FAM, now Gamin, has always worked without issues. Never > had any problems. Good for you, but you are not the only user of the code. > > FAM support in Courier gets built only if the configure script sees > FAM installed on your system. If you have FAM or Gamin installed, but > the attempt to initialize the library fails, something is seriously > and fundamentally broken. Your system is not stable. Some library or > configuration file got overwritten, misconfigured, or corrupted. I don't think anyone has talked about library init failing. There has been talk of a fully installed FAM/gamin consuming excessive resources and there has been talk of problems installing courier-imap on computers with no FAM/gamin whatsoever. The latter might be mistaken for library init failing, but is really abot courier-imap assuming the library is there when it isn't or shouldn't be. > > On RPM-based distributions this often happens when stuff gets > installed by manually compiling it and installing it, by hand, rather > than building RPM packages proper, and installing them using rpm. When > that happens, inter-package dependencies cannot be reliably tracked by > rpm, and the system becomes unstable. Either core system components > get overwritten by newer but incompatible versions of those > components, or core components get removed even though other > components may depend on them; in both cases due to rpm not being able > to properly track dependencies of software that was not installed > using rpm. No, this is about keeping dependencies OPTIONAL at runtime, especially when everything comes as .rpm or .deb or .pkg or other precompiled package formats. Noone lost track of dependencies, but the courier-imap code assumes a static uniform world where all computers running a single binary are identical to what the build machine looked like at the moment when the binary was built. ------------------------------------------------------------------------------ _______________________________________________ Courier-imap mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap
