Re: what could be causing empty log/current files?

On Tue, 17 Jun 2008, Daryl Tester wrote:

> jaymax wrote:
> 
> > permissions as recommended according to Levine's text, it should have shown
> >        status: local 0/10 remote 0/20
> > Could anyone say what I might have missed

I don't know what the issue is there, sorry.


> I don't think tcpserver issues a status line until the program has 
> terminated, so you won't see anything in the logs until a connection has 
> been made.

That's not a tcpserver status line, though. That's qmail-send. (listing 
the number of local and remote deliveries in progress) And, if in verbose 
mode, tcpserver prints a status message immediately (otherwise it prints 
nothing, AFAIR).

e.g.
$ tcpserver -vDRHl 0 0 9999 ./do-stuff.sh
#### no connection yet ####
tcpserver: status: 0/40
#### vvv first connection vvv ####
tcpserver: status: 1/40
tcpserver: pid 15264 from 127.0.0.1
tcpserver: ok 15264 0:127.0.0.1:9999 :127.0.0.1::53235


> This is why I typically stick an echo early in the run script (if using 
> daemontools) so that you can see when the process starts.