Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <3BB60F12.91DB302D@wapme-systems.de>
Date: Sat, 29 Sep 2001 20:12:34 +0200
From: Stipe Tolj <tolj AT wapme-systems DOT de>
Organization: Wapme Systems AG
X-Mailer: Mozilla 4.7 [de]C-CCK-MCD QXW0322b  (WinNT; I)
X-Accept-Language: de,en
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: qmail-1.03: any volunteers?!
References: <3BB50D84 DOT 20049 DOT 858F0A AT localhost>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

> Well it worked, the problem was, there was no trigger, no fifo. If you send
> an email to the smtpd, it writes this down in a directory and triggers the
> fifo. If the fifo is read by the transport program (inject?) and if there is
> a notice, it will look in the dir and send off what is there.
> To get it up and running, I generated a file in the trigger dir so 's.th.'
> was found, the program thinks there is a fifo (looks like a file), and don't
> report errors, but it works not like a trigger.  The inject tool is eating
> up the cpu because it always thinks the fifo is triggered.

Ohhh, that may be the reason why qmail-send is usually running on 99%
CPU time, even while the system is enough operatable for other things
:((

> The mail is sent off, of course. I built the injector with a sleep of some
> seconds so it doesn't burn my pentium, but this is not the solution.

indeed. -- a sleep() would be at least a work-around for the CPU burn
state.

> Best thing that makes sense here is to find a way to substitute mkfifo,
> or the functionality it provides, Corinna said s.th. with socket calls
> would be possible.

any ideas how?!

> That would be a great thing for cygwin. I have no idea (unfortunately), but i
> think a 'pseudo trigger' would be nice, s.th. that looks like a fifo (a file?)
> and that acts like a fifo (-> socket). You put s.th in at one end which waits
> until someone pulls it out at the other end.
> 
> There are also named pipes at in windows, maybe they can be assimilated?
> (Are we Borg enough to assimilate?)

don't know :)

Stipe

tolj AT wapme-systems DOT de
-------------------------------------------------------------------
Wapme Systems AG

Münsterstr. 248
40470 Düsseldorf

Tel: +49-211-74845-0
Fax: +49-211-74845-299

E-Mail: info AT wapme-systems DOT de
Internet: http://www.wapme-systems.de
-------------------------------------------------------------------
wapme.net - wherever you are

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/