We developed a small server program that run on a DJI Phantom that runs Openwrt.   16KB shared mem ringbuffer is used.   This is the first time we write a Openwrt software and use syslog to log debug info of the program.   We read a post http://www.phantompilots.com/viewtopic. … mp;t=13496, http://www.rcgroups.com/forums/showpost … count=6497 claimed that it is easy to overflow a OPENWRT log file system and implied that the OPENWRT log file system has bugs.   We wonder if there is a safe way to log the program info without using syslog. 

The post is long and here is the statment that :
3. Every time when I use the app, it keeps generating /var/log/xxx.vpu.dat files (0-4kB) and occupying very limited internal storage of the aircraft. Imagine, what will happen when a PC running out/low of disk space. Firmware upgrade or basically anything might crash in low storage condition, who knows.

The app may not create those files explicitly, but likely a harmful side product to the aircraft.

(Last edited by rctaco on 26 Aug 2014, 10:14)

Can't find the post you refer to and its not clear to me what your actual question is.
What do you mean with overflow? What kind of bugs are implied?

We are developing a flight logger that log the DJI Phantom drone flight info to a android, iOS device.    The drone runs OPENWRT.   16KB shared mem ringbuffer is used.   We wrote a server program running on the drone to monitor the serial port data and then send them back to the android, iOS device.   

http://www.phantompilots.com/viewtopic. … mp;t=13496 is a review of our app.  The server program is running on OPENWRT and used the syslog to log the server program debug info.  The review stated that 

-->>>
3. Every time when I use the app, it keeps generating /var/log/xxx.vpu.dat files (0-4kB) and occupying very limited internal storage of the aircraft. Imagine, what will happen when a PC running out/low of disk space. Firmware upgrade or basically anything might crash in low storage condition, who knows.
<<<--

it implied that syslog function call will overflow the buffer used in the log file system and crash the whole system.   

That is the reason why we wonder  if there is a safe way to log the program debug info without using syslog.

The path "/var/log/xxx.vpu.dat" resembles nothing done by OpenWrt, it must be generated by something else not part of vanilla OpenWrt.