On Tue, May 08, 2007 at 12:03:39PM +1000, Hamish Moffatt wrote:
> And now it's fairly broken; incoming TCP connections get refused (I'm
> running inetd, netstat shows the sockets, but connections are not
> accepted), and busybox's ash reports "-sh: can't access tty; job control
> turned off". Hmm :
On Tue, May 08, 2007 at 12:03:48AM +0200, Denis Vlasenko wrote:
> On Monday 07 May 2007 14:23, Hamish Moffatt wrote:
> > syslog messages are being truncated. This happens regardless of their
[..]
> Yes, I mistakenly thought that BUFSIZ is big enough and used
> BUFSIZ-sized buffer for data in syslog
On Monday 07 May 2007 14:23, Hamish Moffatt wrote:
> Hi,
>
> I've just installed busybox 1.4.2 on an embedded ARM system using uclibc
> 0.9.28.3. (I'll try 1.5.0 next but the web site warns it may not be
> stable yet.)
>
> syslog messages are being truncated. This happens regardless of their
> so
On 07/05/07 ? ? 22:23, Hamish Moffatt wrote:
> Hi,
>
> I've just installed busybox 1.4.2 on an embedded ARM system using uclibc
> 0.9.28.3. (I'll try 1.5.0 next but the web site warns it may not be
> stable yet.)
>
> syslog messages are being truncated. This happens regardless of their
> source (
Hi,
I've just installed busybox 1.4.2 on an embedded ARM system using uclibc
0.9.28.3. (I'll try 1.5.0 next but the web site warns it may not be
stable yet.)
syslog messages are being truncated. This happens regardless of their
source (klogd, logger, other programs), with the exception of syslogd
