X-Git-Url: http://git.tuebingen.mpg.de/?p=paraslash.git;a=blobdiff_plain;f=README.afs;h=51625667b652706b1cae1ccea4db0ddff6526f66;hp=edd2d17be98591391a7d3ceab0a820cf12b77763;hb=a4f75cecaaee538edb7aae3f0ff19168a1dab59d;hpb=4f01c486bb70a27f614cdc9c07a2b8d653db7605 diff --git a/README.afs b/README.afs index edd2d17b..51625667 100644 --- a/README.afs +++ b/README.afs @@ -178,18 +178,19 @@ is not set, the empty string is matched against the pattern. bitrate ~ frequency ~ channels ~ + num_played ~ Takes a comparator ~ of the set {<, =, <=, >, >=, !=} and a number . Matches an audio file iff the condition ~ is satisfied where val is the corresponding value of the audio file -(bitrate in kbit/s, frequency in Hz, channel count, value of the -year tag). +(value of the year tag, bitrate in kbit/s, frequency in Hz, channel +count, play count). The year tag is special as its value is undefined if the audio file has no year tag or the content of the year tag is not a number. Such audio files never match. Another difference is the special treatment if the year tag is a two-digit number. In this case either 1900 or -2000 are added to the tag value, depending on whether the number is +2000 are added to the tag value depending on whether the number is greater than 2000 plus the current year. @@ -252,27 +253,27 @@ debugging info. Almost all paraslash executables have a brief online help which is displayed by using the -h switch. The --detailed-help option prints the full help text. -para_fsck tries to fix your database. Use --force (even if your name -isn't Luke) to clean up after a crash. However, first make sure -para_server isn't running before executing para_fsck if para_fsck -complains about busy (dirty) tables. para_fsck also contains an option -to dump the contents of the database to the file system. +If para_server crashed or was killed by SIGKILL (signal 9), it +may refuse to start again because of "dirty osl tables". In this +case you'll have to run the oslfsck program of libosl to fix your +database. It might be necessary to use --force (even if your name +isn't Luke). However, make sure para_server isn't running before +executing oslfsck --force. If you don't mind to recreate your database you can start from scratch by removing the entire database directory, i.e. - rm -rf ~/.paraslash/afs_database + rm -rf ~/.paraslash/afs_database-0.4 -Note that this removes all tables, in particular attribute definitions -and data, and all playlist and mood definitions. +Be aware that this removes all attribute definitions, all playlists +and all mood definitions. -para_fsck operates on the osl-layer, i.e. it fixes inconsistencies -in the database but doesn't know about the contents of the tables -contained therein. Use +Although oslfsck fixes inconsistencies in database tables it doesn't +care about the table contents. To check for invalid table contents, use para_client check -to print out bad entries, e.g.missing audio files or invalid mood -definitions. +This prints out references to missing audio files as well as invalid +playlists and mood definitions. Still having problems? mailto: Andre Noll