mirror of
				https://github.com/scottlamb/moonfire-nvr.git
				synced 2025-10-30 00:05:03 -04:00 
			
		
		
		
	few small markdown tweaks
This commit is contained in:
		
							parent
							
								
									489fda6abe
								
							
						
					
					
						commit
						5bba71345c
					
				| @ -38,7 +38,7 @@ make this possible: | |||||||
|   drives costing about $100), so we can afford to keep many camera-months of |   drives costing about $100), so we can afford to keep many camera-months of | ||||||
|   both streams on disk. |   both streams on disk. | ||||||
| * decoding and analyzing only select "key" video frames (see | * decoding and analyzing only select "key" video frames (see | ||||||
|   [wikipedia](https://en.wikipedia.org/wiki/Video_compression_picture_types). |   [wikipedia](https://en.wikipedia.org/wiki/Video_compression_picture_types)). | ||||||
| * off-loading expensive work to a GPU. Even the Raspberry Pi has a | * off-loading expensive work to a GPU. Even the Raspberry Pi has a | ||||||
|   surprisingly powerful GPU. |   surprisingly powerful GPU. | ||||||
| * using [HTTP Live Streaming](https://en.wikipedia.org/wiki/HTTP_Live_Streaming) | * using [HTTP Live Streaming](https://en.wikipedia.org/wiki/HTTP_Live_Streaming) | ||||||
|  | |||||||
| @ -426,7 +426,7 @@ These invariants are updated through the following procedure: | |||||||
|    against the given database. This lock is not released until program shutdown. |    against the given database. This lock is not released until program shutdown. | ||||||
| 2. Query `garbage` table and `next_recording_id` field in the `stream` table. | 2. Query `garbage` table and `next_recording_id` field in the `stream` table. | ||||||
| 3. `unlink()` all the sample files associated with garbage rows, ignoring | 3. `unlink()` all the sample files associated with garbage rows, ignoring | ||||||
|    `ENOENT. |    `ENOENT`. | ||||||
| 4. For each stream, `unlink()` all the existing files with recording ids >= | 4. For each stream, `unlink()` all the existing files with recording ids >= | ||||||
|    `next_recording_id`. |    `next_recording_id`. | ||||||
| 4. `fsync()` the sample file directory. | 4. `fsync()` the sample file directory. | ||||||
|  | |||||||
| @ -41,7 +41,7 @@ created), although if you do a re-install of Moonfire, in particular a much | |||||||
| newer version, it is a good idea to run it again as requirements and pre-requisites | newer version, it is a good idea to run it again as requirements and pre-requisites | ||||||
| may have changed. Running the script multiple times should not have any negative effects. | may have changed. Running the script multiple times should not have any negative effects. | ||||||
| 
 | 
 | ||||||
| *WARNING* It is quite possible that during the running of the setup script, | *Note:* It is quite possible that during the running of the setup script, | ||||||
| in particular during the building of libavutil you will see several compiler | in particular during the building of libavutil you will see several compiler | ||||||
| warnings. This, while undesirable, is a direct result of the original | warnings. This, while undesirable, is a direct result of the original | ||||||
| developers not cleaning up the cause(s) of these warnings. They are, however, | developers not cleaning up the cause(s) of these warnings. They are, however, | ||||||
| @ -62,9 +62,9 @@ This script will perform all steps necessary to build a complete Moonfire | |||||||
| setup. If there are no build errors, this script will then automatically | setup. If there are no build errors, this script will then automatically | ||||||
| invoke the install script (see below). | invoke the install script (see below). | ||||||
| 
 | 
 | ||||||
| There are two options you may pass to this script. The first is "-B" which | There are two options you may pass to this script. The first is `-B` which | ||||||
| means "build only". In other words, this will stop the automatic invocation | means "build only". In other words, this will stop the automatic invocation | ||||||
| of the install script. The other option available is "-t" and causes the | of the install script. The other option available is `-t` and causes the | ||||||
| script to ignore the results of any tests. In other words, even if tests | script to ignore the results of any tests. In other words, even if tests | ||||||
| fail, the build phase will be considered successful. This can occasionally | fail, the build phase will be considered successful. This can occasionally | ||||||
| be useful if you are doing development, and have temporarily broken one | be useful if you are doing development, and have temporarily broken one | ||||||
| @ -80,7 +80,7 @@ like this: | |||||||
| This script will copy various files resulting from the build to the correct | This script will copy various files resulting from the build to the correct | ||||||
| locations. It will also create a "service configuration" for systemctl that | locations. It will also create a "service configuration" for systemctl that | ||||||
| can be used to control Moonfire. This service configuration can be prevented | can be used to control Moonfire. This service configuration can be prevented | ||||||
| by using the "-s" option to this script. It will also prevent the automatic | by using the `-s` option to this script. It will also prevent the automatic | ||||||
| start of this configuration. | start of this configuration. | ||||||
| 
 | 
 | ||||||
| ## Configuration variables | ## Configuration variables | ||||||
|  | |||||||
		Loading…
	
	
			
			x
			
			
		
	
		Reference in New Issue
	
	Block a user