View Full Version : [ViX_Misc] Debug logs time format
Hi there.
Quick question please.
If I want to analyse my debug log files I can see the time the last log file was created but I'm not sure how to convert the number in the log file to a "time". Can someone please explain.
e.g. in this log snippet below I can see the numbers 46772.542 but how does that relate to the time of the log entry??
Sorry to be a bit dim.
also.... All of my log files seem to be an hour ahead of realtime. Is that something to do with BST. the time on my box is correct (EPG)
Thanks
Paul
< 46373.873> [Trashcan] found following trashcan's: ['/media/hdd/movie/.Trash']
< 46373.873> [Trashcan] looking in trashcan /media/hdd/movie/.Trash
< 46373.887> [Trashcan] /media/hdd/movie/.Trash: Size: 66620044956
< 46373.905> [Trashcan] /media/hdd/movie/.Trash: Size now: 66620044956
< 46373.962> [Task] job Components.Task.Job name=Cleaning Trashes #tasks=1 completed with [] in None
< 46375.837> [DVBCAHandler] no more services
< 46376.839> [eDVBFrontend2] close frontend
< 46376.839> [eDVBFrontend2] sendTone allowed only in feSatellite (2)
< 46495.097> [Task] job Components.Task.Job name=SoftcamCheck #tasks=1 completed with [] in None
< 46772.535> [Console] command: ('hdparm', 'hdparm', '-y', '/dev/sda')
< 46772.535> [eConsoleAppContainer] Starting hdparm
< 46772.536> [Console] pid = 29502
< 46772.542> [Console] finished: ('hdparm', 'hdparm', '-y', '/dev/sda')
e.g. in this log snippet below I can see the numbers 46772.542 but how does that relate to the time of the log entryIt's the time in seconds since the system (not enigma2) booted.
If you look near the top of the log, when enigma2 was staring up, you'll find an entry as it checks the time, either against NTP or your transponder time(?). So you can related one time-since-boot to the wall-clock, and hence work out what all other time-since-boot entries refer to.
e.g. mine has lines like:
< 45.154> [PowerTimer] PowerTimerEntry(type=autostandby, begin=Fri Apr 10 19:58:53 2020)
< 45.165> [PowerTimer] PowerTimerEntry(type=autodeepstandby, begin=Fri Apr 10 19:58:53 2020)
...
< 45.174> [ABM-Scheduler][AutoScheduleTimer] Schedule Disabled at Fri 10 Apr 2020 19:58:23 BST
...
< 45.187> [ImageManager] Backup Schedule Disabled at (now=Fri 10 Apr 2020 19:58:23 BST)
...
< 45.190> [BackupManager] Backup Time set to Fri 10 Apr 2020 22:00:00 BST (now=Fri 10 Apr 2020 19:58:23 BST)
Perfect thanks.
ATV is simpler. It shows the actual time and date - its Sh*t in many other ways though so I can live with that :-)
what if the log splits every 4Mb and the startup was 5 log files ago though?
If I look at eh top of my latest log I see only this - I can't see a date/time when the system booted. How do I know which log file to look at to get that date?
This is my last (current) log file (truncated to 1st few minutes):
< 14.823> [Avahi] avahi_timeout_new
< 14.823> [Avahi] avahi_watch_new(3 0x1)
< 14.823> [Avahi] avahi_timeout_update
< 14.823> [Avahi] avahi_timeout_new
< 14.824> [Avahi] avahi_timeout_free
< 14.824> [Avahi] avahi_timeout_new
< 14.824> [Avahi] avahi_timeout_free
< 14.824> [Avahi] avahi_timeout_new
< 14.824> [Avahi] avahi_timeout_free
< 14.824> [Avahi] avahi_timeout_new
< 14.825> [Avahi] avahi_timeout_free
< 14.825> [Avahi] avahi_timeout_new
< 14.825> [Avahi] avahi_timeout_free
< 14.825> [Avahi] avahi_timeout_new
< 14.825> [Avahi] avahi_timeout_free
< 14.826> [Avahi] client state: 1
< 14.826> [Avahi] Not running yet, cannot browse for type _e2stream._tcp.
< 14.826> [eInit] + (1) Background File Eraser
< 14.826> [eInit] + (5) Tuxtxt
< 14.826> [eInit] + (8) graphics acceleration manager
< 14.826> [eInit] + (9) GFBDC
< 14.826> [fb] /dev/fb0: 24300k video mem
< 14.830> [fb] double buffering available!
< 14.847> [gFBDC] resolution: 1280x720x32 stride=5120, 17100kB available for acceleration surfaces.
< 14.847> [eInit] + (9) gLCD
< 14.847> [eFbLCD] /dev/fb1: No such file or directory
< 14.847> [eFbLCD] framebuffer /dev/fb1 not available
< 14.847> [eDboxLCD] xres=132, yres=64, bpp=8 lcd_type=1
< 14.847> [eLCD] (132x64x8) buffer 0x32cba8 8448 bytes, stride 132
< 14.848> [eLCD] (132x64x8) buffer 0x3957e0 8448 bytes, stride 132
< 14.848> [gLCDDC] resolution: 132x64x8 stride=132
< 14.848> [eInit] + (9) Font Render Class
< 14.848> [Font] initializing lib...
< 14.856> [Font] loading fonts...
< 14.856> [Font] Intializing font cache, using max. 4MB...
[Enigma2] PYTHONPATH: /usr/lib/enigma2/python
[Enigma2] DVB_API_VERSION 5 DVB_API_VERSION_MINOR 11
ENIGMA_DEBUG_LVL=4
< 14.856> [eInit] + (10) gRC
< 14.856> [gRC] thread created successfully
< 14.856> [eInit] + (15) eWindowStyleManager
< 14.856> [eInit] + (20) DVB-CI UI
< 14.856> [eInit] + (20) UHF Modulator
< 14.856> [eRFmod] couldnt open /dev/rfmod0: No such file or directory
< 14.856> [eInit] + (20) RC Input layer
< 14.856> [eInit] + (20) misc options
< 14.856> [eInit] + (20) AVSwitch Driver
< 14.856> [eAVSwitch] failed to open /dev/dbox/fp0 to monitor vcr scart slow blanking changed: No such file or directory
< 14.856> [eInit] + (21) input device driver
< 14.856> [eRCInputEventDriver] devicename=front panel
< 14.856> [eRCInputEventDriver] devicename=front panel
< 14.857> [eRCDeviceInputDev] device "front panel" is a remotecontrol
< 14.857> [eRCInputEventDriver] devicename=dreambox remote control (native)
< 14.857> [eRCInputEventDriver] devicename=dreambox remote control (native)
< 14.857> [eRCDeviceInputDev] device "dreambox remote control (native)" is a remotecontrol
< 14.857> [eRCInputEventDriver] devicename=dreambox advanced remote control (native)
< 14.857> [eRCInputEventDriver] devicename=dreambox advanced remote control (native)
< 14.857> [eRCDeviceInputDev] device "dreambox advanced remote control (native)" is a remotecontrol
< 14.857> [eRCInputEventDriver] devicename=front panel
< 14.857> [eRCInputEventDriver] devicename=front panel
< 14.857> [eRCDeviceInputDev] device "front panel" is a remotecontrol
< 14.857> [eRCInputEventDriver] devicename=RC for hdmi_cec
< 14.857> [eRCInputEventDriver] devicename=RC for hdmi_cec
< 14.857> [eRCDeviceInputDev] device "RC for hdmi_cec" is a remotecontrol
< 14.857> [eInputDeviceInit] Found 5 input devices.
< 14.857> [eInit] + (22) Hdmi CEC driver
< 14.956> [gRC] main thread is non-idle! display spinner!
< 14.956> [gRC] enabelSpinner: no spinner DC!
< 15.151> [eInit] + (30) eActionMap
< 15.151> [eInit] + (35) CI Slots
< 15.151> [CI] scanning for common interfaces..
< 15.151> [CI] Slot: 0 setSource: A
< 15.152> [CI] eDVBCIInterfaces setInputSource(0, A)
< 15.152> [CI] eDVBCIInterfaces setInputSource(1, B)
< 15.152> [CI] eDVBCIInterfaces setInputSource(2, C)
< 15.152> [CI] eDVBCIInterfaces setInputSource(3, D)
< 15.152> [CI] done, found 1 common interface slots
< 15.153> [CI] Streaming CI finish interface not advertised, assuming "tuner" method
< 15.153> [eInit] + (35) CA handler
< 15.153> [eInit] + (40) eServiceCenter
< 15.153> [eServiceCenter] settings instance.
< 15.153> [eInit] + (41) eServiceFactoryDVD
< 15.155> [eInit] + (41) eServiceFactoryWebTS
< 15.155> [eInit] + (41) eServiceFactoryTS
< 15.155> [eInit] + (41) eServiceFactoryHDMI
< 15.155> [eInit] + (41) eServiceFactoryM2TS
< 15.155> [eInit] + (41) eServiceFactoryMP3
< 15.155> [eInit] + (41) eServiceFactoryFS
< 15.155> [eInit] + (41) eServiceFactoryDVB
< 15.155> [eInit] + (41) Encoders
< 15.156> [eInit] + (41) Stream server
< 15.157> [Avahi] Not running yet, cannot register type _e2stream._tcp.
< 15.157> [eInit] reached rl 70
< 15.157> [eDVBDB] ---- opening lame channel db
< 15.158> [eDVBDB] reading services (version 4)
< 15.169> [eDVBDB] loaded 78 channels/transponders and 1096 services
< 15.169> [eDVBResourceManager] scanning for frontends..
< 15.169> [eDVBFrontend0] opening frontend
< 15.169> [eDVBFrontend0] opening frontend
< 15.169> [eDVBFrontend0] frontend 0 has DVB API 50a
< 15.170> [eDVBFrontend0] close frontend
< 15.170> [eDVBFrontend1] opening frontend
< 15.170> [eDVBFrontend1] opening frontend
< 15.196> [eDVBFrontend1] frontend 1 has DVB API 50a
< 15.196> [eDVBFrontend1] close frontend
< 15.197> [eDVBFrontend2] opening frontend
< 15.197> [eDVBFrontend2] opening frontend
< 15.222> [eDVBFrontend2] frontend 2 has DVB API 50a
< 15.222> [eDVBFrontend2] close frontend
< 15.222> [eDVBAdapterLinux] get demux 0
< 15.222> [eDVBAdapterLinux] get demux 1
< 15.222> [eDVBAdapterLinux] get demux 2
< 15.222> [eDVBAdapterLinux] get demux 3
< 15.222> [eDVBAdapterLinux] get demux 4
< 15.222> [eDVBAdapterLinux] get demux 5
< 15.222> [eDVBAdapterLinux] get demux 6
< 15.222> [eDVBAdapterLinux] get demux 7
< 15.222> [eDVBResourceManager] found 1 adapter, 3 frontends(3 sim) and 8 demux
< 15.223> [eDVBLocalTimeHandler] RTC not ready... wait for transponder time
< 15.223> [eEPGCache] Initialized EPGCache (wait for setCacheFile call now)
< 15.224> [MAIN] Loading spinners...
< 15.255> [MAIN] found 18 spinner!
< 15.255> [setIoPrio] best-effort level 3 ok
< 15.429> [Image Type] release
< 15.429> [Image Version] 5.3
< 15.429> [Image Build] 019
< 16.956> [gRC] main thread is non-idle! display spinner!
< 28.616> [Geolocation] Error : Geolocation data not available! (Reason: [Errno -2] Name or service not known)
< 28.709> [Misc_Options] 12Vdetect cannot open /proc/stb/misc/12V_output: No such file or directory
< 28.716> [Console] command: mount /dev/mmcblk0p1 /tmp/multibootcheck
< 28.716> [eConsoleAppContainer] Starting /bin/sh
< 28.717> [Console] pid = 2193
< 28.723> [Console] command: /bin/mount /dev/mmcblk0p1 /tmp/multibootcheck
< 28.723> [eConsoleAppContainer] Starting /bin/sh
< 28.723> [Console] pid = 2197
< 28.743> [Console] command: umount /tmp/multibootcheck
< 28.743> [eConsoleAppContainer] Starting /bin/sh
< 28.743> [Console] pid = 2225
< 28.755> [Harddisk] enumerating block devices...
< 28.774> [Harddisk] new Harddisk sdb -> /dev/sdb -> /dev/sdb
< 28.814> [Harddisk] new Harddisk sda -> /dev/sda -> /dev/sda
< 28.814> [Harddisk] new Harddisk start Idle
< 28.814> [Console] command: ('hdparm', 'hdparm', '-S0', '/dev/sda')
< 28.814> [eConsoleAppContainer] Starting hdparm
< 28.815> [Console] pid = 2226
< 28.847> [Harddisk] enumerating network mounts...
< 28.855> [Config] Config file loaded ok...
< 28.919> [Skin] Warning: Skin file 'skin_user.xml' does not exist!
< 28.921> [Skin] Skin '/usr/share/enigma2/ViXBMC_1080_Confluence/skin.xml' added successfully.
< 28.925> [Skin] Skin '/usr/share/enigma2/display/skin_default/skin_display.xml' added successfully.
< 28.927> [Skin] Skin '/usr/share/enigma2/skin_subtitles.xml' added successfully.
< 28.932> [Skin] Skin '/usr/share/enigma2/skin_default/skin.xml' added successfully.
< 29.019> [Picon] adding path: /media/hdd/picon/
< 29.063> [NimManager] Reading satellites.xml
< 29.208> [NimManager] Reading cables.xml
< 29.381> [NimManager] Reading terrestrial.xml
< 29.605> [InitNimManager] enable combined tuner type(s) DVB-T2
< 29.606> [SecConfigure] sec config cleared
< 29.606> [eDVBFrontend] setSlotInfo for dvb frontend 0 to slotid 0, descr Si2169D, need rotorworkaround No, enabled Yes, DVB-S2 Yes
< 29.606> [eDVBFrontend] setSlotInfo for dvb frontend 1 to slotid 1, descr Si2169D, need rotorworkaround No, enabled Yes, DVB-S2 Yes
< 29.606> [eDVBFrontend] setSlotInfo for dvb frontend 2 to slotid 2, descr Si2168, need rotorworkaround No, enabled Yes, DVB-S2 No
< 29.607> [SecConfigure] slot: 0 configmode: simple
< 29.607> [SecConfigure] diseqcmode: single
< 29.607> [SecConfigure] slot: 1 configmode: simple
< 29.607> [SecConfigure] diseqcmode: single
< 29.608> [SecConfigure] sec config completed
< 29.637> SystemInfo MachineBuild h7
< 29.637> SystemInfo BoxType zgemmah7
< 29.637> SystemInfo BrandOEM airdigital
< 29.637> SystemInfo DisplayType 7segment
< 29.637> SystemInfo HaveRCA False
< 29.637> SystemInfo getHaveDVI False
< 29.637> SystemInfo HaveYUV False
< 29.637> SystemInfo HaveSCART False
< 29.637> SystemInfo HaveAVJACK True
< 29.637> SystemInfo HaveSCARTYUV False
< 29.638> SystemInfo HaveHDMI True
< 29.638> SystemInfo MachineMtdRoot mmcblk0p3
< 29.638> VideoWizard has_dvi False
< 29.638> VideoWizard has_rca False
< 29.638> VideoWizard has_jack True
< 29.638> VideoWizard has_scart False
< 29.638> AVSwitch Scart-YPbPr False
< 29.638> AVSwitch no_YPbPr True
< 29.638> AVSwitch yellow_RCA_no_scart True
< 29.638> AVSwitch no_yellow_RCA__no_scart False
< 29.688> [MovieSelection] Bluray Player is not installed: cannot import name BlurayPlayer
< 29.808> [eDVBDB] loading bouquet... /etc/enigma2//bouquets.tv
< 29.809> [eDVBDB] loading bouquet... /etc/enigma2//userbouquet.abm.terrestrial_finder.main.tv
< 29.813> [eDVBDB] 796 entries in Bouquet userbouquet.abm.terrestrial_finder.main.tv
< 29.813> [eDVBDB] loading bouquet... /etc/enigma2//userbouquet.abm.terrestrial_finder.1.tv
< 29.814> [eDVBDB] 67 entries in Bouquet userbouquet.abm.terrestrial_finder.1.tv
< 29.814> [eDVBDB] loading bouquet... /etc/enigma2//userbouquet.abm.terrestrial_finder.100.tv
< 29.815> [eDVBDB] 6 entries in Bouquet userbouquet.abm.terrestrial_finder.100.tv
< 29.815> [eDVBDB] loading bouquet... /etc/enigma2//userbouquet.abm.terrestrial_finder.201.tv
< 29.815> [eDVBDB] 6 entries in Bouquet userbouquet.abm.terrestrial_finder.201.tv
< 29.815> [eDVBDB] loading bouquet... /etc/enigma2//userbouquet.abm.terrestrial_finder.230.tv
< 29.816> [eDVBDB] 7 entries in Bouquet userbouquet.abm.terrestrial_finder.230.tv
< 29.816> [eDVBDB] loading bouquet... /etc/enigma2//userbouquet.abm.terrestrial_finder.260.tv
< 29.816> [eDVBDB] 2 entries in Bouquet userbouquet.abm.terrestrial_finder.260.tv
< 29.816> [eDVBDB] loading bouquet... /etc/enigma2//userbouquet.abm.terrestrial_finder.670.tv
< 29.816> [eDVBDB] 15 entries in Bouquet userbouquet.abm.terrestrial_finder.670.tv
< 29.816> [eDVBDB] loading bouquet... /etc/enigma2//userbouquet.abm.terrestrial_finder.separator.tv
< 29.817> [eDVBDB] 114 entries in Bouquet userbouquet.abm.terrestrial_finder.separator.tv
< 29.817> [eDVBDB] loading bouquet... /etc/enigma2//userbouquet.abm.terrestrial_finder.hd.tv
< 29.822> [eDVBDB] 1002 entries in Bouquet userbouquet.abm.terrestrial_finder.hd.tv
< 29.823> [eDVBDB] loading bouquet... /etc/enigma2//userbouquet.abm.sat_282_sky_uk.101.tv
< 29.824> [eDVBDB] 201 entries in Bouquet userbouquet.abm.sat_282_sky_uk.101.tv
< 29.824> [eDVBDB] loading bouquet... /etc/enigma2//userbouquet.abm.sat_282_sky_uk.201.tv
< 29.825> [eDVBDB] 101 entries in Bouquet userbouquet.abm.sat_282_sky_uk.201.tv
< 29.825> [eDVBDB] loading bouquet... /etc/enigma2//userbouquet.abm.sat_282_sky_uk.301.tv
< 29.826> [eDVBDB] 50 entries in Bouquet userbouquet.abm.sat_282_sky_uk.301.tv
< 29.826> [eDVBDB] loading bouquet... /etc/enigma2//userbouquet.abm.sat_282_sky_uk.350.tv
< 29.827> [eDVBDB] 52 entries in Bouquet userbouquet.abm.sat_282_sky_uk.350.tv
< 29.827> [eDVBDB] loading bouquet... /etc/enigma2//userbouquet.abm.sat_282_sky_uk.401.tv
< 29.828> [eDVBDB] 90 entries in Bouquet userbouquet.abm.sat_282_sky_uk.401.tv
< 29.828> [eDVBDB] loading bouquet... /etc/enigma2//userbouquet.abm.sat_282_sky_uk.490.tv
< 29.828> [eDVBDB] 10 entries in Bouquet userbouquet.abm.sat_282_sky_uk.490.tv
< 29.828> [eDVBDB] loading bouquet... /etc/enigma2//userbouquet.abm.sat_282_sky_uk.501.tv
< 29.829> [eDVBDB] 60 entries in Bouquet userbouquet.abm.sat_282_sky_uk.501.tv
< 29.829> [eDVBDB] loading bouquet... /etc/enigma2//userbouquet.abm.sat_282_sky_uk.560.tv
< 29.829> [eDVBDB] 21 entries in Bouquet userbouquet.abm.sat_282_sky_uk.560.tv
< 29.829> [eDVBDB] loading bouquet... /etc/enigma2//userbouquet.abm.sat_282_sky_uk.580.tv
< 29.830> [eDVBDB] 22 entries in Bouquet userbouquet.abm.sat_282_sky_uk.580.tv
< 29.830> [eDVBDB] loading bouquet... /etc/enigma2//userbouquet.abm.sat_282_sky_uk.601.tv
< 29.830> [eDVBDB] 60 entries in Bouquet userbouquet.abm.sat_282_sky_uk.601.tv
< 29.830> [eDVBDB] loading bouquet... /etc/enigma2//userbouquet.abm.sat_282_sky_uk.660.tv
< 29.831> [eDVBDB] 42 entries in Bouquet userbouquet.abm.sat_282_sky_uk.660.tv
< 29.831> [eDVBDB] loading bouquet... /etc/enigma2//userbouquet.abm.sat_282_sky_uk.701.tv
< 29.832> [eDVBDB] 101 entries in Bouquet userbouquet.abm.sat_282_sky_uk.701.tv
< 29.832> [eDVBDB] loading bouquet... /etc/enigma2//userbouquet.abm.sat_282_sky_uk.801.tv
< 29.833> [eDVBDB] 100 entries in Bouquet userbouquet.abm.sat_282_sky_uk.801.tv
< 29.833> [eDVBDB] loading bouquet... /etc/enigma2//userbouquet.abm.sat_282_sky_uk.900.tv
< 29.833> [eDVBDB] 49 entries in Bouquet userbouquet.abm.sat_282_sky_uk.900.tv
< 29.833> [eDVBDB] loading bouquet... /etc/enigma2//userbouquet.abm.sat_282_sky_uk.950.tv
< 29.834> [eDVBDB] 32 entries in Bouquet userbouquet.abm.sat_282_sky_uk.950.tv
< 29.834> [eDVBDB] loading bouquet... /etc/enigma2//userbouquet.abm.sat_282_sky_uk.981.tv
< 29.834> [eDVBDB] 13 entries in Bouquet userbouquet.abm.sat_282_sky_uk.981.tv
< 29.834> [eDVBDB] loading bouquet... /etc/enigma2//userbouquet.abm.sat_282_sky_uk.993.tv
< 29.835> [eDVBDB] 8 entries in Bouquet userbouquet.abm.sat_282_sky_uk.993.tv
< 29.835> [eDVBDB] loading bouquet... /etc/enigma2//userbouquet.abm.sat_282_sky_uk.1000.tv
< 29.835> [eDVBDB] 21 entries in Bouquet userbouquet.abm.sat_282_sky_uk.1000.tv
< 29.835> [eDVBDB] loading bouquet... /etc/enigma2//userbouquet.abm.sat_282_sky_uk.1020.tv
< 29.835> [eDVBDB] 11 entries in Bouquet userbouquet.abm.sat_282_sky_uk.1020.tv
< 29.836> [eDVBDB] loading bouquet... /etc/enigma2//userbouquet.abm.sat_282_sky_uk.1030.tv
< 29.836> [eDVBDB] 19 entries in Bouquet userbouquet.abm.sat_282_sky_uk.1030.tv
< 29.836> [eDVBDB] loading bouquet... /etc/enigma2//userbouquet.abm.sat_282_sky_uk.1050.tv
< 29.836> [eDVBDB] 1 entries in Bouquet userbouquet.abm.sat_282_sky_uk.1050.tv
< 29.836> [eDVBDB] loading bouquet... /etc/enigma2//userbouquet.abm.sat_282_sky_uk.separator.tv
< 29.841> [eDVBDB] 952 entries in Bouquet userbouquet.abm.sat_282_sky_uk.separator.tv
< 29.841> [eDVBDB] loading bouquet... /etc/enigma2//userbouquet.abm.sat_282_sky_uk.hd.tv
< 29.847> [eDVBDB] 1010 entries in Bouquet userbouquet.abm.sat_282_sky_uk.hd.tv
< 29.847> [eDVBDB] loading bouquet... /etc/enigma2//userbouquet.dbe00.tv
< 29.848> [eDVBDB] 28 entries in Bouquet userbouquet.dbe00.tv
< 29.848> [eDVBDB] loading bouquet... /etc/enigma2//userbouquet.LastScanned.tv
< 29.851> [eDVBDB] 463 entries in Bouquet userbouquet.LastScanned.tv
< 29.851> [eDVBDB] 34 entries in Bouquet bouquets.tv
< 29.851> [eDVBDB] loading bouquet... /etc/enigma2//bouquets.radio
< 29.852> [eDVBDB] loading bouquet... /etc/enigma2//userbouquet.abm.terrestrial_finder.main.radio
< 29.856> [eDVBDB] 733 entries in Bouquet userbouquet.abm.terrestrial_finder.main.radio
< 29.856> [eDVBDB] loading bouquet... /etc/enigma2//userbouquet.abm.sat_282_sky_uk.main.radio
< 29.861> [eDVBDB] 997 entries in Bouquet userbouquet.abm.sat_282_sky_uk.main.radio
< 29.861> [eDVBDB] loading bouquet... /etc/enigma2//userbouquet.favourites.radio
< 29.862> [eDVBDB] 0 entries in Bouquet userbouquet.favourites.radio
< 29.862> [eDVBDB] 3 entries in Bouquet bouquets.radio
< 29.862> [eDVBDB] Renumbering...
< 29.875> [Time By]: NTP
< 29.875> [eDVBLocalTimeHandler] disable sync local time with transponder time!
< 29.875> [eEPGCache] time updated.. but cache file not set yet.. dont start epg!!
< 29.876> [Console] command: /usr/bin/ntpdate-sync
< 29.876> [eConsoleAppContainer] Starting /bin/sh
< 29.876> [Console] pid = 2227
< 30.987> [Image Flashed] 2020-02-12
< 31.017> [Ipkg] Added to OPKG destinations: /media/hdd
< 31.017> [Ipkg] Added to OPKG destinations: /
< 31.034> [Skin] Loading included file '/usr/share/enigma2/skin_default.xml'.
< 31.084> [Font] adding font /usr/share/fonts/Roboto-Bold.ttf -> Regular
< 31.090> [Font] adding font /usr/share/fonts/Roboto-BoldItalic.ttf -> Italic
< 31.094> [Font] adding font /usr/share/fonts/Roboto-Black.ttf -> Bold
< 31.099> [Font] adding font /usr/share/fonts/Roboto-BlackItalic.ttf -> Boldit
< 31.103> [Font] adding font /usr/share/fonts/nmsbd.ttf -> Subtitlefont
< 31.109> [Font] adding font /usr/share/fonts/lcd.ttf -> LCD
< 31.111> [Font] adding font /usr/share/fonts/ae_AlMateen.ttf -> Replacement
< 31.114> [Font] adding font /usr/share/fonts/tuxtxt.ttf -> Console
< 31.116> [Font] adding font /usr/share/fonts/andale.ttf -> Fixed
< 31.128> [Skin] Loading included file '/usr/share/enigma2/skin.xml'.
< 31.150> [Font] adding font /usr/share/fonts/OpenSans-Regular.ttf -> Subs
< 31.157> [Font] adding font /usr/share/fonts/OpenSans-Italic.ttf -> Subsi
< 31.163> [Font] adding font /usr/share/fonts/OpenSans-Semibold.ttf -> Subsb
< 31.170> [Font] adding font /usr/share/fonts/OpenSans-SemiboldItalic.ttf -> Subsz
< 31.452> [fb] double buffering available!
< 31.490> [gFBDC] resolution: 1920x1080x32 stride=7680, 8100kB available for acceleration surfaces.
< 31.494> [Skin] Loading included file '/usr/share/enigma2/ViXBMC_1080_Common/skin_ViXBMC_1080_Common.xml'.
< 31.537> [Skin] Loading included file '/usr/share/enigma2/ViXBMC_1080_Common/skin_ViXBMC_1080_Common_Templates.xml'.
< 31.549> [Font] adding font /usr/share/enigma2/ViXBMC_1080_Common/fonts/Roboto-Regular.ttf -> Regular
< 31.555> [Font] adding font /usr/share/enigma2/ViXBMC_1080_Common/fonts/Roboto-Bold.ttf -> screentitle
< 31.559> [Font] adding font /usr/share/enigma2/ViXBMC_1080_Common/fonts/Roboto-Regular.ttf -> menulist
< 31.559> [Font] adding font /usr/share/enigma2/ViXBMC_1080_Common/fonts/Roboto-Bold.ttf -> clock
< 31.560> [Font] adding font /usr/share/enigma2/ViXBMC_1080_Common/fonts/Roboto-Bold.ttf -> date
< 31.560> [Font] adding font /usr/share/enigma2/ViXBMC_1080_Common/fonts/OpenSans-Regular.ttf -> channelselectionservice
what if the log splits every 4Mb and the startup was 5 log files ago though?Then look in the first log?
This is my last (current) log file (truncated to 1st few minutes): Actually to its first 17s, so you didn't get as far as the records that would have equated the two times.
The other thing you can do is press a key "now" and you'll get a log entry "now".
Then look in the first log?As far as I can see that is not how it works.
Once per hour after enigma start the debug log file length is checked and if it is oversize the file is truncated to the maximum size limit by removing excess from the start of the file. No "new" log file is created.
https://github.com/OpenViX/enigma2/blob/Dev/lib/python/Screens/LogManager.py#L96
abu baniaz
11-04-20, 00:56
Can we look at bsod.cpp and make times real like ATV and PurE2?
As far as I can see that is not how it works.
Once per hour after enigma start the debug log file length is checked and if it is oversize the file is truncated to the maximum size limit by removing excess from the start of the file. No "new" log file is created.
https://github.com/OpenViX/enigma2/blob/Dev/lib/python/Screens/LogManager.py#L96Ah, yes. You're right.
This is (or was) a bug, as there is something about the way it does (did) truncation that resulted in the file positioning being incorrect (resulting in garbage in the log?).
I did once look at rotating logs instead, but the way logs are written mitigated against doing so. (It's not enigma2 writing the log but the parent shell.)
But a simple keypress "now" will always work.
Can we look at bsod.cpp and make times real like ATV and PurE2?With a crash log the filename shows the time of the crash.
This description text needs sorting out.
59886
Hi All,
I must be doing log checking differently :-)
I tend to use my PC and a program like WinSCP to look at the logs remotely so no "now" keypress in that situation.
I personally think that it would be worth considering making the times real.
What prompted this question is that I was getting a spinner for 2 seconds on the hour every hour and I was intrigued to try and discover what it was that was doing it. No a crash so no crash log (and thus no time stamp at the beginning of the log file). I thought it would be a simple case of looking at the debug log and looking at the correct times each hour but it turned out to not be so simple so I kind of gave up. I know that is not important but... for the casual user like me who might like to report a potential issue it would make sense to make it as easy as possible to get the accurate debug info as quickly as possible. The easier it is the more likely other bugs might get discovered.
Cheers guys
Paul
I think a human readable time output is a good idea when debugging via the console too, although I see from the history of eerror.cpp that there are advantages to the timestamp value.
eDebug: its time to timestamp debug messages
Debug messages will be prefixed with <secs.usecs> time information
This is the same time as used but the kernel for printk messages.
Note printk uses sec.usecs so enigma and kernel messages can
readily be identified.
I think a human readable time output is a good idea when debugging via the console too, although I see from the history of eerror.cpp that there are advantages to the timestamp value.
Couldn't both formats be used?
is there a linux command to:
1) show the time of the start
2) input a value like 14440.223 and get the time from the start time.
If so that would be really useful (Sorry I am a linux virgin).
e.g. something like:
showrelativetime 14400.223
Relativetime is : >> Sat 14th June 2020 @ 20:01:20
Also, Sorry to be really stupid but where is the "keypress now" option in the screens ?
I have this:
59887
if both formats were used then to keep everyone happy perhaps every 10th entry could be the real time e.g.
..
..
14400.100 bla bla bla
14410.222 bla bla
14500.123 bla
14600.333 bla bla
2020.04.11:15:30:20.10 bla bla bla
14750.233
14800.333
Probably better to have another field, I reckon the date isn't terribly important.
<4739496.666 09:58.03.324> [eDVBSectionReader] DMX_SET_FILTER pid=18
or
<4739496.666> 09:58.03.324 [eDVBSectionReader] DMX_SET_FILTER pid=18
The inclusion of the human readable time could be optional - the timestamp is on a flag
My only question is whether the < > surrounding the timestamp is significant for any existing tools. Can someone with a bit more Linux background comment?
Agree about the date. I was just thinking that doing it every 10 or so entries would stop the actual debug info being shoved too far over to the right
Any option would be fine by me :-)
What prompted this question is that I was getting a spinner for 2 seconds on the hour every hour and I was intrigued to try and discover what it was that was doing it. No a crash so no crash log (and thus no time stamp at the beginning of the log file). I thought it would be a simple case of looking at the debug log and looking at the correct times each hour but it turned out to not be so simple so I kind of gave up.lThe log contains an entry for showing the spinner when it does so. Just look for "spinner".
Or look at the log when (just after) the spinner has been showing.
My only question is whether the < > surrounding the timestamp is significant for any existing tools. Can someone with a bit more Linux background comment?It make parsing out timestamps simpler if you wish to do so (there may be debug lines without them - the current debug line contain some file-system device entry info near the start that someone has left in place for some reason - or just forgotten about....
How about this...
<03:08:18.3133> [ABM-Scheduler][Scheduleautostart] reason(0), session <__main__.Session instance at 0xb20ef490>
<03:08:18.3135> [ABM-Scheduler][Scheduleautostart] AutoStart Enabled
<03:08:18.3137> [ABM-Scheduler][AutoScheduleTimer] Schedule Disabled at Sun 12 Apr 2020 03:08:18 CEST
<03:08:18.3139> [XMLTVImport] autostart (0) occured at 1586653698.31
<03:08:18.3147> [XMLTVImport] WakeUpTime now set to -1 (now=1586653698)
<03:08:18.3152> [JoyneScan-Scheduler][Scheduleautostart] reason(0), session <__main__.Session instance at 0xb20ef490>
<03:08:18.3153> [JoyneScan-Scheduler][Scheduleautostart] AutoStart Enabled
<03:08:18.3155> [JoyneScan-Scheduler][AutoScheduleTimer] Schedule Disabled at Sun 12 Apr 2020 03:08:18 CEST
<03:08:18.3156> [ImageManager] AutoStart Enabled
<03:08:18.3157> [ImageManager] Backup Schedule Disabled at (now=Sun 12 Apr 2020 03:08:18 CEST)
<03:08:18.3158> [BackupManager] AutoStart Enabled
<03:08:18.3159> [BackupManager] Backup Schedule Disabled at (now=Sun 12 Apr 2020 03:08:18 CEST)
<03:08:18.3411> [Skin] Processing screen 'Screensaver', position=(0, 0), size=(1920 x 1080) for module 'Screensaver'.
https://github.com/Huevos/enigma2/commit/d97ae81e454d27b68f93dae8b566b9c300e78dcf
abu baniaz
12-04-20, 02:27
Looks good. Can we try adding a date? No need for year, IMO.
Not sure of the value of the date.
Options are here:
http://www.cplusplus.com/reference/ctime/tm/
Date without year is a problem as it is not clear if it is mm/dd or dd/mm.
Also, adding pointless chars to the left of the log means the log is right shifted maybe making it necessary at times to scroll horizontally to read it.
Also this has a big negative point which is, if you are trying to determine the time difference in seconds between one event and another having the log time in seconds is much easier to cope with.
e.g. if I want to know how long a blindscan took to complete I just subtract one stamp from another. In clock format that is not possible.
Probably better to have another field, I reckon the date isn't terribly important.
<4739496.666 09:58.03.324> [eDVBSectionReader] DMX_SET_FILTER pid=18
or
<4739496.666> 09:58.03.324 [eDVBSectionReader] DMX_SET_FILTER pid=18
The inclusion of the human readable time could be optional - the timestamp is on a flag
If we go with stamp and date we only need the u_sec on one field.
I got as far as this yesterday https://github.com/SimonCapewell/enigma2/tree/time-debug-logging, but as ever, getting the C++ build working again after an absence seems to be a black art. Main thing here is that you can chose to have either format or both.
Simon can you make this configurable from the UI? If not how do we change from one to the other?
What box are you using? ARM or MIPS?
It'd be an environment variable, so perhaps the UI would be able to manipulate the current environment value. If not, you should be able to set it in the shell before starting the e2 executable.
I think mine is a MIPS box - it's an ET8500
That variable is static ( static int debugTime = 3; ). Does that mean it is immutable? I have no idea of the rules of cpp.
Could be set in the shell script? The shell script can read the settings file to decide what value to send to enigma. That is more or less how debug logs are enabled/disabled at the current time.
Static just means it's shared across all instances, like Python's
class MyClass:
myStatic = 5
def __init__(self):
print MyClass.myStatic
myInstance = 23
Yes, you should be able to test the flag from the shell using
export ENIGMA_DEBUG_TIME=0
enigma2
Date without year is a problem as it is not clear if it is mm/dd or dd/mm.??? Print the month as its short text form (as your original example did). strftime() lets you do anything you want from a template.
Couple of build errors:
https://github.com/Huevos/enigma2/commit/c222ff6b7fec6288057272c88fd6713b9abca281
https://github.com/Huevos/enigma2/commit/51ec140196c3ad018af225799bac8b465844ecf3
Binary attached.
Output looks like this:
< 13.047> 14:21:06.2154 [fb] double buffering available!
< 13.069> 14:21:06.2365 [gFBDC] resolution: 1280x720x32 stride=5120, 17100kB available for acceleration surfaces.
< 13.069> 14:21:06.2366 [eInit] + (9) gLCD
< 13.069> 14:21:06.2367 [eFbLCD] /dev/fb1: No such file or directory
< 13.069> 14:21:06.2368 [eFbLCD] framebuffer /dev/fb1 not available
< 13.069> 14:21:06.2369 [eDboxLCD] xres=132, yres=64, bpp=8 lcd_type=2
< 13.069> 14:21:06.2369 [eLCD] (132x64x8) buffer 0x6c2aa8 8448 bytes, stride 132
< 13.069> 14:21:06.2369 [eLCD] (132x64x8) buffer 0x6b7198 8448 bytes, stride 132
< 13.069> 14:21:06.2369 [gLCDDC] resolution: 132x64x8 stride=132
< 13.069> 14:21:06.2370 [eInit] + (9) Font Render Class
< 13.069> 14:21:06.2370 [Font] Initializing lib...
Now we need to try make it configurable from UI.
MIPs one works great. Output with an export ENIGMA_DEBUG_TIME=2 is good:
15:07:31.634 [eInit] - (41) eServiceFactoryDVD
15:07:31.634 [eInit] - (41) eServiceFactoryWebTS
15:07:31.635 [eInit] - (41) eServiceFactoryTS
15:07:31.635 [eInit] - (41) eServiceFactoryHDMI
15:07:31.635 [eInit] - (41) eServiceFactoryM2TS
15:07:31.635 [eInit] - (41) eServiceFactoryMP3
15:07:31.636 [eInit] - (41) eServiceFactoryFS
I am appreciating all the work here everyone. I am really grateful this is going to happen. :-) :-) :-)
This adds configurable option from the user interface...
https://github.com/Huevos/enigma2/commit/55d5debb32323d7888dc323a1891e12d7d0c7511
abu baniaz
13-04-20, 01:04
Would there be negative effects of making default = local time + boot?
Abu, do whatever you think is good. I just set the default to the current format. In the end there is no default anyway because debug log is disabled by default. So this will only apply when enabling debug logs and saving that screen.
Would there be negative effects of making default = local time + boot?
Any chance of making this the default, most crash logs are being posted without this setting, but this format is so much easier to read.
abu baniaz
27-10-20, 20:36
Please submit a pull request.
Please submit a pull request.
I haven't a clue how to do that. I know you've given details, but ......
Any chance of making this the default, most crash logs are being posted without this setting, but this format is so much easier to read.
No. The added text on the left make logs harder to read due to the need to sideways scroll.
No. The added text on the left make logs harder to read due to the need to sideways scroll.
Crikey, never expected that as a reason, still, I don't need to waste my time learning how to submit a pull request.
Please explain what help you think it is to debugging having clock output at the start of every line.
I live in "real time", not "number time", so I can see in the logs when something happened without any guesswork.
You're able to see if the log corresponds to what a poster is saying without the need to find time updates. Even then it isn't easy.
If someone says a timer didn't start at 19:00 or a cronjob doesn't work, you can get there straight away.
Same with autotimer, you can see when it ran.
Keypresses can be difficult to pinpoint, but in real time you can tie them in with other activity.
Regular error messages might as well be random error messages without the clock.
I use notepad++ to view logs, I reckon 90% of lines don't need scrolling, and probably 99% of those lines that do only need scrolling if there is something significant to view.
But it sounds like I'm the only one who finds them useful, and 99% of the rest of us probably don't even know you can switch the clock on.
I spend a lot of the time debug‘ing especially at the moment and the ability to run without any time stamp is a real positive, means I can run side by side comparisons... so by default my setting is option 0.
I spend a lot of the time debug‘ing especially at the moment and the ability to run without any time stamp is a real positive, means I can run side by side comparisons... so by default my setting is option 0.
That's you analysing your debug logs, how you do that is fine, but that's not what happens when Mr Average posts a debug log.
It's a pointless discussion anyway, the decision has already been taken.
abu baniaz
29-10-20, 17:58
I spend a lot of the time debug‘ing especially at the moment and the ability to run without any time stamp is a real positive, means I can run side by side comparisons... so by default my setting is option 0.
You are not using the default or proposed, so you are not affected. Anyway, for people who want to compare difference in log output, I attach different layout of debug logs.
Not as if many people will know how to convert the timestamps, so boot time on its own is useless barring a few people. The decision has been made, so that's that. Should there be a change in position, my suggestion is now to make default = local time. Number of characters is the same!
Edit:
For easier comparison
Boot
<136448.3578> [eDVBServicePMTHandler] tune failed.
Local time
16:36:12.4169 [eDVBServicePMTHandler] tune failed.
Boot + local time
< 1589.0473> 16:59:53.7282 [eDVBServicePMTHandler] tune failed.
I spend a lot of the time debug‘ing especially at the moment and the ability to run without any time stamp is a real positive, means I can run side by side comparisons...Stripping them out is trivial.
And if you're comparing them you already have copies, so a quick awk command solves your problem on those occasions when you need it.
Stripping them out is trivial.
And if you're comparing them you already have copies, so a quick awk command solves your problem on those occasions when you need it.
Why strip them if you can just turn them off?
Why strip them if you can just turn them off?
My debug logs have them switched on, so you (or whoever) would perhaps need to strip them off.
("0", _("none")),
("1", _("boot time")),
("2", _("local time")),
("3", _("boot time and local time")) ])
Maybe make "3" "local time and boot time", then a simple scroll right (or is it left?) will eliminate the local time for anyone who wants to.
abu baniaz
30-10-20, 11:08
How does changing default prevent others from turning the stamps off or using any format they want?
it sounds like I'm the only one who finds them useful
No, I use local time only in my debug logs too. It makes it much easier to ensure I'm looking at the correct debug output from a test run in the console. If I'm looking at performance, then I chuck a profile trace around the code I'm interested in (using Tools/Trace.py) and filter the debug output using grep.
BrokenUnusableAccount
30-10-20, 16:30
Why strip them if you can just turn them off?
So you can get them back later if you need them.
Why strip them if you can just turn them off?Because you then might wish to know what they were in retrospect, but can't.
Having something you can remove is much better than not having something you can't add.
Ok, well set your boxes up how you want them. That is why this is a user option.
abu baniaz
30-10-20, 23:06
The default should be the most useful one to majority of people.
How does changing default prevent others from turning the stamps off or using any format they want?
Missed this, I was posting at the same time.
Nothing to stop others from changing the timestamp to whatever they want.
Lots of users don't even know what a crashlog is until they're asked to attach one, so they always end up with the default setting.
Had a look at the debug log in this post, lots going on, loads of timers and 2 recordings ending up zero length.
No chance (for me) working out what was going on, but local time might have helped. :sofahide:
https://www.world-of-satellite.com/showthread.php?63450-Can-t-add-news-channels-to-AutoBouquetsMaker&p=504785&viewfull=1#post504785
No chance (for me) working out what was going on, but local time might have helped.
You can work it all out from this line:
< 37.7348> [Timezones] Local time is 'Wed 04-Nov-2020 18:02:19' - UTC time is 'Wed 04-Nov-2020 18:02:19'.
You can work it all out from this line:
And what about the other 30,615 lines ??
Just add the difference in seconds :)
You can work it all out from this line:....Actually, this one is more helpful:
< 48.4063> [XMLTVImport] autostart (0) occured at 1604512949.75As you can use those two numbers in a simple Perl one-liner to get the time from any tag. e.g.:
[parent]: perl -le 'print scalar localtime(shift()-48.4063+1604512949.75)' 38.7348
Wed Nov 4 18:02:20 2020
[parent]: perl -le 'print scalar localtime(shift()-48.4063+1604512949.75)' 170706.9567
Fri Nov 6 17:26:48 2020
Actually, this one is more helpful:
As you can use those two numbers in a simple Perl one-liner to get the time from any tag. e.g.:
[parent]: perl -le 'print scalar localtime(shift()-48.4063+1604512949.75)' 38.7348
Wed Nov 4 18:02:20 2020
[parent]: perl -le 'print scalar localtime(shift()-48.4063+1604512949.75)' 170706.9567
Fri Nov 6 17:26:48 2020
There is a much simpler way (that's an understatement), but unfortunately it has been rejected.
I actually use the real-time setting in my debug logs as it's an option. My tongue-in-cheek reply to you was just a joke! I don't really know why this thread is so long - people should use whatever option is most suitable for them. Most users don't have debug logs enabled. It's mostly testers or devs who use them. I think it's great to finally have the option of different time settings in the logfile.
I actually use the real-time setting in my debug logs as it's an option. My tongue-in-cheek reply to you was just a joke! I don't really know why this thread is so long - people should use whatever option is most suitable for them. Most users don't have debug logs enabled. It's mostly testers or devs who use them. I think it's great to finally have the option of different time settings in the logfile.
Totally agree with you
I actually use the real-time setting in my debug logs as it's an option. My tongue-in-cheek reply to you was just a joke! I don't really know why this thread is so long - people should use whatever option is most suitable for them. Most users don't have debug logs enabled. It's mostly testers or devs who use them. I think it's great to finally have the option of different time settings in the logfile.
Why do you use it then, maybe because it's useful?
Most users who are asked to submit debug logs or crash logs don't have real time set, that is the point I'm failing to get across.
Devs and testers can set the option to whatever they want for their logs, but that doesn't affect anybody else's logs.
Maybe I'll just stop looking at them in the future.
...
Maybe I'll just stop looking at them in the future.
@ccs - I certainly didn't realise that you were making the point that the time format default was to make it easier for you to analyse debug logs. When I'm looking at submitted logs I just accept the format for what it is and if relevant try to work out when specific events occur from the seconds offset from a known timestamp. Please don't stop looking at submitted logs - your contributions are greatly valued.
abu baniaz
08-11-20, 17:18
I am pretty sure we are the first image to offer actual time in logs. It is the most useful layout.
I don't know why there is such objection to it being the default. Almost all the objectors aren't even using the current default.
The days of ViX being geared for benefit of end user are definitely over!
I am pretty sure we are the first image to offer actual time in logs. It is the most useful layout.Personally I find time-since-boot more useful, as it's easier to judge progressions from a single number.
It does help to have an anchor to real time, though, so writing such an entry when a new log is opened (rotated because of size) would be helpful, as would ensuring there is such a record in a crashlog.
abu baniaz
09-11-20, 03:15
What is useful to you or me is irrelevant. We can set what we want.
As already posted you are more than capable of using scripts to alter the debug log to interrogate it. Very few of our users or testers are in the same boat as you.
The default should be what is useful to majority of people. When they look at their logs or upload them, it should be simple to read/follow.
As an aside - I had a look at my OpenATV debug log. It uses realtime only. No options.
The days of ViX being geared for benefit of end user are definitely over!
You are joking right? What is the point of the image if not for the benefit of end users?
No, when do you see me post jokes? Just look here. People getting banned for complaining about an item that has been in Vix for many years
https://www.world-of-satellite.com/showthread.php?63406-Menubutton-in-5-4
========= deleted ========
abu baniaz
13-11-20, 19:53
Well Abu, when I 1st joined you had no issues hitting me for a really minor criticism - so OK for you to take actions against users, but not anybody else
I don't recall banning you. Please remind me which post you made that led me to do that. If banning you was unwarranated, I will offer my apology.
People should not be silenced for airing cristicsm of changes. A discussion can be had as to why, and see if a happy medium can be found. And people can understand why the changes have been made and why the loss had to be suffered.
This only works when people do not want to be deceptive
I don't recall banning you. Please remind me which post you made that led me to do that. If banning you was unwarranated, I will offer my apology.
People should not be silenced for airing cristicsm of changes. A discussion can be had as to why, and see if a happy medium can be found. And people can understand why the changes have been made and why the loss had to be suffered.
This only works when people do not want to be deceptive
Abu, I wanted to forget it (thats why I deleted it, before your response) ...but then you have to your 5 pennyworth regardless
abu baniaz
13-11-20, 20:22
Abu, I wanted to forget it (thats why I deleted it, before your response) ...but then you have to your 5 pennyworth regardless
You obviously have not forgotten. And how can I respond to a deleted post? If I owe you an apology, it is only right that I do.
However, you have now accused me of double standards. So you need to substantiate this attack on my honour and integrity.
You obviously have not forgotten. And how can I respond to a deleted post? If I owe you an apology, it is only right that I do.
However, you have now accused me of double standards. So you need to substantiate this attack on my honour and integrity.
I don‘t need to do anything - cool down Abu
abu baniaz
13-11-20, 20:46
I don‘t need to do anything - cool down Abu
You don't have to do anything.
You have accused me of double standards. Where is your evidence?
abu baniaz
13-11-20, 21:24
Found it:
I gave you an infraction for your comment to PeterJ, one of the developers. I did not ban you.
https://www.world-of-satellite.com/showthread.php?46150-Warning-for-twol-Insulted-Staff
Can we please keep on topic here.
For the record I'd prefer the default left as is, its a user configurable option anyway.
For the record I'd prefer the default left as is, its a user configurable option anyway.
I don't understand your logic, the reason for the suggested change is for (inexperienced) users who haven't the faintest idea what a crash log is until they're asked to post one.
By then it's too late.
If someone can explain why "local time" is so much worse than "boot time" then fine.
I find it easier to read, others who have said they have changed to "local time" probably do as well.
It's seems very strange to me that such a trivial commit is being rejected out of hand.
I don't understand your logic, the reason for the suggested change is for (inexperienced) users who haven't the faintest idea what a crash log is until they're asked to post one.
By then it's too late.I agree with that.
Powered by vBulletin® Version 4.2.5 Copyright © 2024 vBulletin Solutions Inc. All rights reserved.