Opened 14 years ago
Closed 12 years ago
#154 closed defect/bug (worksforme)
more robustness for log file handling
| Reported by: | udo | Owned by: | somebody |
|---|---|---|---|
| Priority: | major | Milestone: | version 0.2.0 |
| Component: | core | Version: | |
| Severity: | Keywords: | ||
| Cc: |
Description
navit 0.1.0 from 08 jun 2008
gpx log files appear as 0 byte after a trip of 35 minutes, and back with ipaq h2210 suspended in between.
<log type="gpx" data="track_%Y%m%d%i.gpx" flush_size="1048576" flush_time="900" />
was due toe log not being in vehicle block. adjust navit.xml and do not log when outside the vehicle block?
Change History (4)
comment:1 Changed 14 years ago by cp15
comment:2 Changed 14 years ago by udo
Today I got 0 byte files as well even though stuff was configured the right way.
<vehicle name="udo" enabled="yes" active="1" follow="4" source="file://dev/ttyS0" color="#0000ff" color2="#ff0000"> <log type="gpx" data="track_%Y%m%d%i.gpx" flush_size="1048576" flush_time="900" />
</vehicle>
comment:3 Changed 14 years ago by KaZeR
- Milestone set to version 0.1.0
comment:4 Changed 12 years ago by kazer
- Resolution set to worksforme
- Status changed from new to closed
2yo bug, i'm closing it. If it still applies, please reopen. Apologies for a such delayed answer.
Usually the xml parser gives an error when a tag is at an unexpected position. However in this case the xml parser can't do this, because it is possible to add an log to navit for debugging purposes (record events for later review during the trip).