This will cause the slimserver to search for the ~.nf, and failing that, to recreate it with default values. To refresh the configuration parameters, you can simply delete the /etc/nf file (or rename it to something else). For more verbose messages, start the program with the options of –d_source –d_stdio If the server dies without any visible error messages, check the log file. nf in the home directory of the current user. If you've installed the RPM on a RedHat, MandrakeLinux, or MandrivaLinux system, you can start the server with this command:Īnd check that the daemon is running withĪs part of the debugging support, if there is no /etc/nf file, or if it is not readable when the slimserver starts, it will look for ~.nf that is, the normally hidden file. There is a log file written to /tmp/slimserver.log This can be changed by editing the /etc/sysconfig/slimserver The standard RPM puts the appropriate entries in /etc/rc.d/init.d so that automated startup works as you expect. The standard installation creates a non-priviledged user named "slimserver" (with its own group "slimserver) that is used to own files and directories, and is used as the login account for the slimserver daemon. Note: see the RPM page if you have trouble with SlimServer 6.5 or newer RPM distributions. The Linux RPMs install the software under /usr/local/slimserver There is one critical config file, /etc/nfig There is also a /etc/sysconfig/slimserver that handles startup from /etc/rc/d/init.d 10 slimserver 6.5.0 and 6.5.1 rescan patch.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |