How to stop auto startup & close the service in MAC OS X

hi

How to stop auto startup & close the service in MAC OS X

if i look in activity monitor i can't find the process, there is no serviio process, if i start the serviio console then the service is there but when i right click and click quit, i go to my tv and look for media servers and serviio is still running even though i have quit the console, there is still no serviio service in activity monitor but it is still running.

i would like to know if it is possible to to stop serviio background service auto starting, i know that console does not autostart?

also what is the serviio background service called? java? serviioconsole is there if i start activity monitor, but nothing else serviio?

i have a slow iMac so i need to disable, preferably to items auto starting to make my iMac run faster...

also even from a fresh boot without the serviio console being started by me the media server shows up on my tv..

serviio 152. mac os x..

thank you

oh and also on audio channels which provides better sound keep original or mix to stereo, there are no external speakers just the builtin tv speaker for a 42" panasonic hdtv?

[zip]

Try this: http://wiki.serviio.org/doku.php?id=mac ... _autostart

The solution from wiki doesn't work. My version of serviio is 1.5.2 and operating os - osx el capitan (10.11). After adding settings from wiki, launchd starts serviio java process anyway at each boot.

The solution from wiki doesn't work. My version of serviio is 1.5.2 and operating os - osx el capitan (10.11). After adding settings from wiki, launchd starts serviio java process anyway at each boot.

Same here, I wan't to disable the autostart of Serviio on El Capitan and I found not any solutions...

Indeed, and when u remove serviio file from LaunchDaemons, there is no way to start serviio, propably because starting serviio is associated with this file, systemd launch separate java app with arguments set which is server and then through serviio console app which is next separate app you can communicate with this java server process. i am not sure, just i think it works in that way, anyway for me as a developer this is not proper scheme. because when i want to have serviio server on my mac and i dont want to use it i have to have java process launched in background anyway, and in my situation this is not acceptable. I hope someone from devgroup read this and will try to solve this. launchd should start server when i want to. not always.

[zip]

Hang on, so the solution here doesn't work? viewtopic.php?f=5&t=18820#p100505

1 - keep the serviio .plist in your LauncDaemons folder
2 - edit is as per the wiki
3- restart your Mac

It should not autostart. Then to manually start it, load the service as per http://serviio.org/component/content/article?id=21#q13

Hang on, so the solution here doesn't work? viewtopic.php?f=5&t=18820#p100505

1 - keep the serviio .plist in your LauncDaemons folder
2 - edit is as per the wiki
3- restart your Mac

It should not autostart. Then to manually start it, load the service as per http://serviio.org/component/content/article?id=21#q13

Unfortunately no...

If we had this

<key>Disabled</key>
<true/>

to the .plist, the server doesn't start on login. We can start it manually as you describe but then the console gives the message
"Cannot connect to Servo Server, it does not seem to be running. Exiting..."

However the server is well started because if we load it again with "sudo launchctl load /Library/LaunchDaemons/org.serviio.server.plist", we have the message that the server is already load.

It's well describe here: viewtopic.php?f=5&t=19055

Exactly same problem than freebo99, even if we use
<key>Disabled</key>
<true/>

Instead of
<key>RunAtLoad</key>
<false/>


[zip]

So the Disabled tag works, as it doesn't load on startup.

I assume the RunAtLoad is still present in your file and set to true. That means to start the server once the load call happens.

Once you load it, run this command:

  Code:

sudo launchctl list | grep serviio

You should get back something like

  Code:

XXX      0   org.serviio.server


Then run

  Code:

ps aux | grep serviio

and you should get back the running process (see XXX from above is the process number)

  Code:

root              178   0.0  1.1  4570568 178112   ??  S     8:38am   0:49.45 /Library/Application Support/Serviio/jre/Contents/Home/bin/java -Xmx512M -Xms20M -XX:+UseG1GC -XX:GCTimeRatio=1 -XX:MinHeapFreeRatio=10 -XX:MaxHeapFreeRatio=20 -Djava.net.preferIPv4Stack=true -Djava.awt.headless=true -Dorg.restlet.engine.loggerFacadeClass=org.restlet.ext.slf4j.Slf4jLoggerFacade -Dderby.system.home=/Library/Application Support/Serviio/library -Dserviio.home=/Library/Application Support/Serviio -Dffmpeg.location=/Library/Application Support/Serviio/lib/ffmpeg -Ddcraw.location=/Library/Application Support/Serviio/lib/dcraw -Dserviio.libraryPollerFrequency=5 -classpath /Library/Application Support/Serviio/lib/*:/Library/Application Support/Serviio/config org.serviio.MediaServer
root               XXX   0.0  0.0  2446696   1072   ??  Ss    8:38am   0:00.01 /bin/bash /Library/Application Support/Serviio/bin/serviio.sh

If the process is not there, post the log file at

  Code:

/Library/Application\ Support/Serviio/log


Unfortunetly the only way to completely shutdown serviio is completely remove from mac. Reinstalling for each use is not a option for me. Anyone which have same problems and need more control over app, i propose http://www.universalmediaserver.com i switched to it and work better and faster, its open source and completely free and more robust, controllable and reliable than serviio. ( and UMS doesnt force dedicated graphic card to use, UMS works on integrated all the time - important and big difference on battery usage and heating, i can close the lid without worry that i burn display and i can stream for very long time without power connected)