I have managed to run the command without an error.However the media server is not found (presumably not started) unless i log into Ubuntu and start the script either directly or using the following command'sudo /etc/init.d/PS3MediaServer start'

Same problem here. After booting I checked and the process is not running. The log file contains these lines:

The problem I had with the original script was when I stopped the daemon (/etc/init.d/PS3MediaServer stop) it stopped the media server but it would continue showing on the PS3 because the connection was not terminated. It works fine after the change.

I'm sure this is a noob question, but it seems that the server isn't nearly as chatty when running as a daemon. e.g.- I have to manually search for a media server now, from XMB, whereas with the original PMS.sh, the server would connect and disconnect almost in real-time. I did mod the signal from 2 to 15, but saw no change, the server is still listed on XMB once the PID is killed / service stopped. How would one turn those alive messages back on?[EDIT: my mistake, looks like there's a DNLA hello delay in XMB3.0, when remoteplay is enabled. I was using a PSP to monitor the PS3 while working on the server. My mistake]

Also, my PMS.conf isn't being loaded when using the daemon PMS.sh, not sure how to add this back in. Any help would be greatly appreciated.[EDIT: this is still an issue for me, would someone please let me know how to point the daemon at the PMS.conf file?]

bombino wrote:Also, my PMS.conf isn't being loaded when using the daemon PMS.sh, not sure how to add this back in. Any help would be greatly appreciated.[EDIT: this is still an issue for me, would someone please let me know how to point the daemon at the PMS.conf file?]

what I did was log in as the user who runs PMS.sh, and run it from that directory, in my case /opt/pms/.

according to the script, it's only going to look in the current directory. the PS3MediaServer script cd's to that directory first, then runs the script.

alternatively, you can take your existing PMS.conf, and database/ directory, and copy them to where pms is located.

bombino wrote:Also, my PMS.conf isn't being loaded when using the daemon PMS.sh, not sure how to add this back in. Any help would be greatly appreciated.[EDIT: this is still an issue for me, would someone please let me know how to point the daemon at the PMS.conf file?]

what I did was log in as the user who runs PMS.sh, and run it from that directory, in my case /opt/pms/.

according to the script, it's only going to look in the current directory. the PS3MediaServer script cd's to that directory first, then runs the script.

alternatively, you can take your existing PMS.conf, and database/ directory, and copy them to where pms is located.

hope this helps.

I moved PMS.conf to the app root and it worked like a charm.Thanks very much for the help.

Sorry, just moved to linux and i'm a totally noob to it.I have just configured ps3ms as a "linux service" and it seems to work ok. However, how can i access the GUI so i can change settings? it has to be somewhere since it's running.

In windows, the PS3MS icon will show up in the system tray so you can open the gui, even if it has been started as a service.

I am having the same problem as arie. The daemon only picks up the loopback 'lo' interface when starting at boot and then creates the socket at 0.0.0.0:5001 instead of picking up interface 'eth0' and creating the socket at 192.168.1.100:5001.

Any ideas on how to fix this??I'm using Ubuntu 8.10 and my ps3mediaserver is located in /usr/local/pms

This is what the log file looks like when the daemon starts at boot-up:

I'm trying to get this working on a fresh Jaunty install but the instructions aren't so clear. I intend to work through the issue, just had some questions.

[*]Unzip the script and put it in /etc/init.dI placed the PS3MediaServer file in /etc/init.d - I then renamed the original PMS.sh to PMS.sh.orig and moved the new one into the pms directory, is this correct?

[*]Edit the script (which one? both? seems like both), the only thing you need to edit is the PMS_HOME variable and write your path to PS3 Media Server (in my case /opt/pms). Looking through the PS3MediaServer file there is no "PMS_HOME" in the file. There is a "PMS_ROOT" which I've set to the directory where I have the pms files.

[*]Edit the PMS_USER and PMS_GROUP variables in the script to the user and group you want to use to launch the PS3 Media Server[*]Make the script executable with command: "sudo chmod +x PS3Mediaserver"[*]If you want to autostart the service on boot type "sudo update-rc.d PS3MediaServer defaults 90"