Re: fsync on large files

Matthias Urlichs (smurf@noris.de)
14 Feb 1999 07:36:14 +0100

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Rogier Wolff: "Re: Interrupts not being raised."
Previous message: Makoto Kato: "BFS filesystem driver for linux 2.2.x"
Maybe in reply to: Alan Curry: "fsync on large files"
Next in thread: Olaf Titz: "Re: fsync on large files"

"Alan Curry" <pacman-kernel@cqc.com> writes:
> So here's what I think the real problem is. On the main machine, there are
> lots of things trying to talk to syslogd. But syslogd can't accept their
> connections because it is contantly fsync'ing, so the other daemons block
> trying to connect.

The real fix for this problem would be to use a syslogd which uses datagram
sockets instead. (Both libc5 and glibc understand them.)

I hacked the Linux syslogd to do that (I'm certainly not the only one to do
that, though). Patch on request.

-- Matthias Urlichs | noris network GmbH | smurf@noris.de | ICQ: 20193661 The quote was selected randomly. Really. | http://www.noris.de/~smurf/

-- Do you smoke after sex? Why, do you know, I've never looked!

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/

Next message: Rogier Wolff: "Re: Interrupts not being raised."
Previous message: Makoto Kato: "BFS filesystem driver for linux 2.2.x"
Maybe in reply to: Alan Curry: "fsync on large files"
Next in thread: Olaf Titz: "Re: fsync on large files"