Yes, we do have FIFO/named pipe problems in -current. I committed a workaround to prevent one particular condition under which my diskless box would hang forever in sendmail processing in /etc/rc by setting a 1 sec timeout on the sleep it hung in. This is nowhere near correct as pointed out by Bruce, but at least my machine boots.
I don't know what the bug is, Alfred looked at it some, but the patch he came up with did not work on my machine. I belive the issue rests there. Poul-Henning In message <[EMAIL PROTECTED]>, Fred Souza writes: > >--GvXjxJ+pjyke8COw >Content-Type: text/plain; charset=us-ascii >Content-Disposition: inline >Content-Transfer-Encoding: quoted-printable > >> Hi, >>=20 >> ports/mail/gensig has a problem. It is supposed to create a named pipe >> (~/.signature) and wait for an application to read from the pipe. It >> allows to have a random signature on every mail. On 4.x and on 5-current >> from last year it works as expected. But since the end of the last year >> or the begin of this year it doesn't anymore. gensig daemonizes itself >> fills the named pipe and then terminates. The content of the named pipe >> stays the same for every mail (no wonder, gensig is gone). > > I had the same problem with signify (which is not on ports). My fix > for it was to force open() to open the file for both read and write > (signify is a Perl script). I can send the patch if you need to see > what I actually did. > > > Fred > > >--=20 >"Death is only a state of mind. >Only it doesn't leave you much time to think about anything else." > >--GvXjxJ+pjyke8COw >Content-Type: application/pgp-signature >Content-Disposition: inline > >-----BEGIN PGP SIGNATURE----- >Version: GnuPG v1.2.1 (FreeBSD) > >iD8DBQE+RoC4KbRS1GgW4fYRAp3xAJ4lA9doM8Dty7aVgvZMePJBgGMT1ACgga17 >6lX0Oy0b4KW8MheO7wZzopI= >=3Ya0 >-----END PGP SIGNATURE----- > >--GvXjxJ+pjyke8COw-- > >To Unsubscribe: send mail to [EMAIL PROTECTED] >with "unsubscribe freebsd-current" in the body of the message > -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
