mirror of
				https://github.com/vdr-projects/vdr.git
				synced 2025-03-01 10:50:46 +00:00 
			
		
		
		
	Version 1.5.1
- Added cDevice::HasCi() so that devices with Common Interface can be avoided when tuning to an FTA channel, thus preserving the CAM resources even on budget DVB cards (suggested by Petri Helin). - Fixed i18n characters for the Hungarian texts (thanks to Thomas Günther). - Now using cPipe instead of popen() in cCommand::Execute() to avoid problems with open file handles when starting background commands (thanks to Reinhard Nissl). - Removed 'assert(0)' from cDvbSpuDecoder::setTime() (thanks to Marco Schlüßler). - Fixed a possible crash when loading an invalid XPM file (thanks to Martin Wache). - Updated satellite names in 'sources.conf' (thanks to Thilo Wunderlich). - Adapted 'libsi' to DVB-S2 (thanks to Marco Schlüßler). - Fixed handling error status in cDvbTuner::GetFrontendStatus() (thanks to Reinhard Nissl). - Shutdown handling has been rewritten (thanks to Udo Richter). - Plugins can now implement the new function WakeupTime() to request VDR to wake up at a particular time (thanks to Udo Richter). - The HUP signal now forces a restart of VDR (thanks to Udo Richter). - cThread::EmergencyExit() has been replaced by ShutdownHandler.RequestEmergencyExit(). - Several references to "button" in a remote control context have been changed to "key" (based on a report from Marko Mäkelä regarding the "Menu button closes" text). The "MenuButtonCloses" parameter in 'setup.conf' has therefore been renamed to "MenuKeyCloses", accordingly. This will result in an "unknown config parameter: MenuButtonCloses" error message in the log file, so you may want to remove that entry from your 'setup.conf' file. - Simplified the error handling in cDvbTuner::GetFrontendStatus() (based on a discussion with Reinhard Nissl). - Updated the Finnish OSD texts (thanks to Rolf Ahrenberg). - Increased the maximum number of DVB devices to 8 (thanks to Rolf Ahrenberg). - The new Setup parameter "Channel entry timeout" can be used to customize the time since the last keypress until a numerically entered channel number is considered complete, and the channel is switched (suggested by Helmut Auer). Setting this parameter to 0 turns off the automatic channel switching, and the user will have to confirm the entry by pressing the "Ok" key.
This commit is contained in:
		
							
								
								
									
										47
									
								
								INSTALL
									
									
									
									
									
								
							
							
						
						
									
										47
									
								
								INSTALL
									
									
									
									
									
								
							@@ -160,30 +160,33 @@ and the next timer event is at least MinEventTimeout minutes in the future
 | 
			
		||||
(see the Setup parameters in MANUAL).
 | 
			
		||||
 | 
			
		||||
The command given in the '-s' option will be called with five parameters.
 | 
			
		||||
The first one is the time (in UTC) of the next timer event (as a time_t
 | 
			
		||||
type number), and the second one is the number of seconds from the current
 | 
			
		||||
time until the next timer event. Your program can choose which one to use
 | 
			
		||||
for programming some sort of hardware device that makes sure the computer
 | 
			
		||||
will be restarted in time before the next timer event. Your program must
 | 
			
		||||
also initiate the actual shutdown procedure of the computer. After this
 | 
			
		||||
your program should return to VDR. VDR will not automatically exit after
 | 
			
		||||
calling the shutdown program, but will rather continue normally until it
 | 
			
		||||
receives a SIGTERM when the computer is actually shut down. So in case
 | 
			
		||||
the shutdown fails, or the shutdown program for some reason decides not to
 | 
			
		||||
perform a shutdown, VDR will stay up and running and will call the shutdown
 | 
			
		||||
program again after another five minutes.
 | 
			
		||||
 | 
			
		||||
If there are currently no timers active, both parameters will be '0'.
 | 
			
		||||
In that case the program shall not set the hardware for automatic restart
 | 
			
		||||
and only perform the system shutdown. A program that uses the second parameter
 | 
			
		||||
to set the hardware for restart must therefore also check whether the first
 | 
			
		||||
parameter is '0'.
 | 
			
		||||
The first one is the time (in UTC) of the next timer event or plugin wakeup
 | 
			
		||||
time (as a time_t type number), and the second one is the number of
 | 
			
		||||
seconds from the current time until the next timer event. Your program can
 | 
			
		||||
choose which one to use for programming some sort of hardware device that
 | 
			
		||||
makes sure the computer will be restarted in time before the next timer
 | 
			
		||||
event. Your program must also initiate the actual shutdown procedure of the
 | 
			
		||||
computer. VDR will not automatically exit after calling the shutdown
 | 
			
		||||
program, but will rather continue normally until it receives a SIGTERM when
 | 
			
		||||
the computer is actually shut down. So in case the shutdown fails, or the
 | 
			
		||||
shutdown program for some reason decides not to perform a shutdown, VDR
 | 
			
		||||
will stay up and running and will call the shutdown program again after a
 | 
			
		||||
while. The command will be started in a separate background session, so it
 | 
			
		||||
can continue to run even after VDR has terminated.
 | 
			
		||||
 | 
			
		||||
The third parameter contains the number of the channel that will be recorded
 | 
			
		||||
by the next timer (or 0 if no timer is present), and the fourth parameter
 | 
			
		||||
contains the file name of the recording as defined in the timer (or an empty
 | 
			
		||||
string if no timer is present). These can be used by the shutdown program to
 | 
			
		||||
show that information on some display interface etc.
 | 
			
		||||
If there are currently no timers active and there is no plugin wakeup
 | 
			
		||||
time, both parameters will be '0'. In that case the program shall not set
 | 
			
		||||
the hardware for automatic restart and only perform the system shutdown.
 | 
			
		||||
A program that uses the second parameter to set the hardware for restart
 | 
			
		||||
must therefore also check whether the first parameter is '0'.
 | 
			
		||||
 | 
			
		||||
If the wakeup time is given by a timer, the third parameter will be the
 | 
			
		||||
number of the channel that will be recorded, otherwise it will be 0. The
 | 
			
		||||
fourth parameter contains the file name of the recording as defined in the
 | 
			
		||||
timer, the name of the plugin that requested the wakeup time, or an empty
 | 
			
		||||
string if no wakeup time is present. These can be used by the shutdown
 | 
			
		||||
program to show that information on some display interface etc.
 | 
			
		||||
 | 
			
		||||
The fifth parameter indicates the reason why the shutdown was requested.
 | 
			
		||||
'0' means this is an automatic shutdown due to some timeout, while '1' means
 | 
			
		||||
 
 | 
			
		||||
		Reference in New Issue
	
	Block a user