Serviio Wiki

User Tools

Site Tools

Trace: • install
howto:solaris:install

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision 		Previous revision
howto:solaris:install [2012/01/18 12:13]
n3mmr created 		howto:solaris:install [2013/01/10 17:35] (current)
zip
Line 1: Line 1:
-The below procedure installs serviio as a service under SMF in Openindiana v 151a and later. +====== How to install serviio to always run at boot in any modern Solaris flavour. ======
-It will likely work just as well, with possibly minor details changed, on Solaris 11, Nexenta and OpenSolaris b148.+
  
 +=== Note that, Solaris or OpenIndiana or any other Solaris descendant, is NOT Linux ===
  
 +<fc #800000>// The differences are by no means obvious, and stem from the large-server heritage of Solaris.
 +Most of the visible differences occur in admin software, but a few quirks exist in userland, too.
 +And the package system is aggressively different.
 +Still, most any Java library is likely to run w/o any problem, and most Linux software
 +can be automatically transformed to run in Solaris descendants.
 +And, given its heritage, Solaris makes for very good and reliable servers. //</fc>
 +
 +The below procedure installs serviio as a service under SMF in Openindiana v 151a and later.
 +It will likely work just as well, with possibly minor details changed, on Solaris 10 or 11, Nexenta and OpenSolaris b134 (possibly earlier versions too).
  
-First, make sure you have the appropriate supporting SW installed:+The serviio console should normally be started from a separate copy of serviio, given the below setup. 
 +In most useful cases, this is anyway the case, since you want serviio running on a server machine, and you run the console from another machine, say your laptop.
  
 +**First, make sure you have the appropriate supporting SW installed:**
 ffmpeg 0.9.1 with rtmp-support, librtmp and lame mp3 can all be found in the sfe-encumbered repository at openindiama.org,  ffmpeg 0.9.1 with rtmp-support, librtmp and lame mp3 can all be found in the sfe-encumbered repository at openindiama.org, 
 http://pkg.openindiana.org/sfe-encumbered/en/index.shtml http://pkg.openindiana.org/sfe-encumbered/en/index.shtml
-from where you can install using the IPS installer, pkg, of your openindiana OI_151a.+from where you can install using the IPS installer, pkg, of your OpenIndiana OI_151a.
  
-Then get the linux tar distro, and extract it under /usr/local/.+**Get the distro and install it**
  
-Now test it by running it manually: +Download the serviio linux tar distro, and extract it under /usr/local/.
  
-prompt> cd /usr/local/serviio-0.6.1 +Create a group "serviio" with a group id > 100:
-prompt> ./bin/serviio.sh& +
-prompt> ./bin/serviio-console.sh &+
  
-Enter the correct address to bind to explicitly on the Status panel, and save. +**//<fc #0000FF>prompt> groupadd -g 103 serviio</fc>//**
-Add media folder trees in the Library panel, and save.+
  
-Check to see that there are discovered renderers listed on the Status panel, and try using serviio from one of those. +and a user "serviio" with home directory /usr/local/serviio-1.1/ and a uid > 100, and with the group serviio as it's primary group
-Be patient, and fiddle around until it works, at least for a few video files.+
  
-When satisfied, right-click on the serviio panel app and choos "exit serviio", or find the processes (they're Java, and you need to be a bit clever to find them) and send them kill signals, or do "kill %%" twice with a few secs in between, if you're in a csh-like shell. +**//<fc #0000FF>prompt> useradd -u 103 -g 103 -d /usr/local/serviio-1.1 serviio</fc>//**
-Make sure serviio is stopped!+
  
-Now create a group "serviio" with a group id > 100:+On my system, 103 was free in both cases, and one might as well use the same number for both.
  
-prompt> groupadd -g 103 serviio+Now, make sure the /usr/local/serviio-1.1 tree is owned by the group serviio and the user serviio: 
 +**//<fc #0000FF> 
 +prompt> cd /usr/local; chown -R serviio:serviio serviio-1.1</fc> 
 +//**
  
-and a user "serviio" with home directory /usr/local/serviio-0.6.1/ and a uid > 100, and with the group serviio as it's primary group+Now test it by running it manually, as user serviio:
  
-prompt> useradd -u 103 -g 103 -d /usr/local/serviio-0.6,1 serviio+<fc #0000FF>//**prompt> pfexec su serviio**//</fc> 
 +**//<fc #0000FF>prompt> cd /usr/local/serviio-1.1  
 +</fc>//** 
 +**//<fc #0000FF> 
 +prompt> ./bin/serviio.sh& 
 +</fc>//** 
 +**//<fc #0000FF> 
 +prompt> ./bin/serviio-console.sh &</fc>//**
  
-On my system, 103 was free in both cases, and one might as well use the same number for both.+Enter the correct address to bind to explicitly on the Status panel, and save. 
 +Add media folder trees in the Library panel, and save.
  
-Now, make sure the /usr/local/serviio-0.6.1 tree is owned by the group serviio and the user serviio: +Check to see that there are discovered renderers listed on the Status panel, and try using serviio from one of those. 
- +Be patient, and fiddle around until it works, at least for a few video files.
-prompt> cd /usr/local; chown -R serviio:serviio serviio-0.6.1+
  
 +When satisfied, right-click on the serviio panel app and choose "exit serviio", or find the processes (they're Java, and you need to be a bit clever to find them) and send them kill signals, or do "kill %%" twice with a few secs in between, if you're in a csh-like shell.
 +Make sure serviio is stopped!
  
 +**Lastly, define a system service that controls Serviio, and start it**
 Save the xml text found at the end of this page in a file "serviio.xml", and put it inside the serviio home dir (see above), and do: Save the xml text found at the end of this page in a file "serviio.xml", and put it inside the serviio home dir (see above), and do:
- +**// 
-prompt> pfexec svccfg validate ~serviio/serviio.xml +<fc #0000FF>prompt> pfexec svccfg validate ~serviio/serviio.xml 
-prompt> pfexec svccfg import ~serviio/serviio.xml+</fc>//** 
 +**//<fc #0000FF> 
 +prompt> pfexec svccfg import ~serviio/serviio.xml</fc>//**
  
 This creates a new service svc:/application/UPnP-AV/serviio:default, which is the complete fmri handle used by the system to start and stop serviio from now on. This creates a new service svc:/application/UPnP-AV/serviio:default, which is the complete fmri handle used by the system to start and stop serviio from now on.
Line 51: Line 72:
 Next enable the service, so that it will start up whenever the machine is booted, and will be restarted if it gets shot down by mistake. Next enable the service, so that it will start up whenever the machine is booted, and will be restarted if it gets shot down by mistake.
  
-prompt> svcadm enable serviio+**//<fc #0000FF>prompt> pfexec svcadm enable serviio 
 +</fc>//**
  
-and as you can see, one needs not use the full fmri, as long as you use enough of the name to make it unique.+You can look at the serviio service by doing  
 +** 
 +//<fc #0000FF>prompt> svcs -l serviio</fc>//**
  
 +and as you can see, you need not use the full fmri, as long as you use enough of the name to make it unique.
  
 +As a final check, just in case, look at /var/tmp/Serviio, and make sure it's owned by serviio, group serviio.
 +This might be wrong if you had an earlier copy running as some user other than serviio, or you did the manual test above not as user serviio.
 +
 +<file>
 ---------serviio.xml file contents------------ ---------serviio.xml file contents------------
 +
 <?xml version="1.0"?> <?xml version="1.0"?>
 <!DOCTYPE service_bundle SYSTEM "/usr/share/lib/xml/dtd/service_bundle.dtd.1"> <!DOCTYPE service_bundle SYSTEM "/usr/share/lib/xml/dtd/service_bundle.dtd.1">
Line 76: Line 106:
             <service_fmri value="svc:/system/filesystem/local"/>             <service_fmri value="svc:/system/filesystem/local"/>
         </dependency>         </dependency>
- 
- 
-         
-         
-         
                  
         <method_context>         <method_context>
Line 86: Line 111:
         </method_context>         </method_context>
  
-        <exec_method type="method" name="start" exec="/usr/local/serviio-0.6.1/bin/serviio.sh" timeout_seconds="60"/>+        <exec_method type="method" name="start" exec="/usr/local/serviio-1.1/bin/serviio.sh" timeout_seconds="60"/>
  
         <exec_method type="method" name="stop" exec=":kill" timeout_seconds="60"/>         <exec_method type="method" name="stop" exec=":kill" timeout_seconds="60"/>
Line 92: Line 117:
         <property_group name="startd" type="framework">         <property_group name="startd" type="framework">
             <propval name="duration" type="astring" value="child"/>             <propval name="duration" type="astring" value="child"/>
-             
-             
             <propval name="ignore_error" type="astring" value="core,signal"/>             <propval name="ignore_error" type="astring" value="core,signal"/>
         </property_group>         </property_group>
Line 100: Line 123:
                          
         </property_group>         </property_group>
-         
                  
         <stability value="Evolving"/>         <stability value="Evolving"/>
Line 116: Line 138:
 </service_bundle> </service_bundle>
 -------end of serviio.xml contents--------------- -------end of serviio.xml contents---------------
 +</file>
howto/solaris/install.1326888788.txt.gz · Last modified: 2012/01/18 12:13 by n3mmr

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki