I've done better. I read the source code :-) You disregard all but the first 128 chars of the file.
Which doesn't play well with the help file which permits # comments and blank lines. All working now - I'll put my commands at the top and leave the comments for after. TVM David In article <[email protected]>, [email protected] (Denys Vlasenko) wrote: > *From:* Denys Vlasenko <[email protected]> > *To:* [email protected] > *CC:* [email protected] > *Date:* Fri, 21 Jan 2011 17:40:01 +0100 > > On Fri, Jan 21, 2011 at 5:20 PM, David Collier > <[email protected]> wrote: > > I have svlogd working very nicely, except it seems to take no > > notice of > > the config file > > > > I have for example ( slightly edited to fit in 72 chars ) > > > > /home/go_netrix # ls -l /var/log/modem_comms > > total 2556 > > -rwxr--r-- 1 root root 999020 Jan 21 15:08 > > @4000...39a175323a13f8.s > > -rwxr--r-- 1 root root 999006 Jan 21 15:39 > > @4000...39a8c5188e4140.s > > -rw-r--r-- 1 root root 1921 Jan 21 15:36 config > > -rw-r--r-- 1 root root 588233 Jan 21 15:57 current > > -rw------- 1 root root 0 Jan 21 14:53 lock > > > > but cat /var/log/modem_comms/config| grep -v \# gives me ( after > > removing blank lines ) > > > > s50000 > > n3 > > t30 > > > > I've tried s 50000 as an alternative. > > > > ======= > > > > having read the man page I can see no way to get it to flag to me > > whether > > it is locating and reading my config file - it seems to default to > > silence if it isn't happy.... and it clearly isn't happy ... > > Run > > strace -oLOG svlogd /var/log/modem_comms </dev/null > > and post LOG here. > > -- > vda > _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
