Home of the Squeezebox™ & Transporter® network music players.
Page 3 of 4 FirstFirst 1234 LastLast
Results 21 to 30 of 39
  1. #21
    Junior Member
    Join Date
    Aug 2014
    Posts
    8

    How this this working?

    How has this been working out?

    I'm interested in helping with this. I could test on Fedora systems if that would help.

  2. #22
    jvromans@squirrel.nl
    Guest

    systemd service file for LMS

    On Sat, 23 Jan 2021 11:49:35 +0000, scytale
    <scytale.9vxglb (AT) no-mx (DOT) forums.slimdevices.com> wrote:

    > How has this been working out?


    There is a logitechmediaserver.service in the debian and raspberry kits
    that works well.

    -- Johan

  3. #23
    jvromans@squirrel.nl
    Guest

    systemd service file for LMS

    On Sat, 23 Jan 2021 15:07:31 +0100, Johan Vromans <jvromans (AT) squirrel (DOT) nl>
    wrote:

    > There is a logitechmediaserver.service in the debian and raspberry kits
    > that works well.


    Oops... It's not in the kit. I don't know where I got it from.

    I've attached it.

    After install of LMS remove SysV script:

    sudo systemctl stop logitechmediaserver.service
    sudo rm /etc/rc*.d/*logitechmediaserver


    Use systemctl script:

    sudo install logitechmediaserver.service.txt /etc/systemd/system/logitechmediaserver.service
    sudo systemctl daemon-reload sudo systemctl enable logitechmediaserver.service
    sudo systemctl start logitechmediaserver.service

    HTH,

    -- Johan


  4. #24
    Quote Originally Posted by jvromans@squirrel.nl View Post
    On Sat, 23 Jan 2021 15:07:31 +0100, Johan Vromans <jvromans (AT) squirrel (DOT) nl>
    wrote:

    > There is a logitechmediaserver.service in the debian and raspberry kits
    > that works well.


    Oops... It's not in the kit. I don't know where I got it from.

    I've attached it.

    After install of LMS remove SysV script:

    sudo systemctl stop logitechmediaserver.service
    sudo rm /etc/rc*.d/*logitechmediaserver


    Use systemctl script:

    sudo install logitechmediaserver.service.txt /etc/systemd/system/logitechmediaserver.service
    sudo systemctl daemon-reload sudo systemctl enable logitechmediaserver.service
    sudo systemctl start logitechmediaserver.service

    HTH,

    -- Johan
    There's nothing attached.

  5. #25
    jvromans@squirrel.nl
    Guest

    systemd service file for LMS

    On Sat, 23 Jan 2021 21:36:22 +0000, mfraser
    <mfraser.9vy7tc (AT) no-mx (DOT) forums.slimdevices.com> wrote:

    > There's nothing attached.


    There is, in my copy of the message...

    Anyway, try
    https://www.squirrel.nl/pub/xfer/upl...NA.service.txt

  6. #26
    Junior Member
    Join Date
    Aug 2014
    Posts
    8
    This looks very useful - especially when debugging start up issues.

    There are better way of spending time than reading through yet another shell start up script.

    What's the best way forward with this? At a guess:

    • fork slimserver-platforms
    • pick one of the linux environments
    • replace the init script with the systemd file
    • make whatever other changes are required to the build configuration to get it to use the unit file instead of the init script
    • build the package
    • install, test and fix until it works across an acceptable range of versions
    • move on to the next environment


    The environments in question would be:

    • debian
    • gentoo
    • redhat


    We don't need to bother with:

    • fedora - superceded by redhat
    • readynas ?????
    • solaris - still uses some kind of shell based init, right?


    Sounds feasible?

  7. #27
    Junior Member
    Join Date
    Aug 2014
    Posts
    8
    Also it looks like at least in Debian it is fairly striaghtforward to use a postinst script to determine if systemd or sysVinit are in use an install the apropriate file:

    Check out this stackexchange answer

    Basically:

    Code:
    if [[ `systemctl` =~ -\.mount ]] 
    then 
      cp $serviceDir/service-systemd /lib/systemd/system/$serviceName.service
    elif [[ -f /etc/init.d/cron && ! -h /etc/init.d/cron ]]
    then 
    cp $serviceDir/service-sysvinit /etc/init.d/$serviceName
    fi

  8. #28
    Babelfish's Best Boy mherger's Avatar
    Join Date
    Apr 2005
    Location
    Switzerland
    Posts
    20,622

    systemd service file for LMS

    > What's the best way forward with this? At a guess:
    >
    > - fork slimserver-platforms
    > - pick one of the linux environments
    > - replace the init script with the systemd file
    > - make whatever other changes are required to the build configuration
    > to get it to use the unit file instead of the init script
    > - build the package
    > - install, test and fix until it works across an acceptable range of
    > versions
    > - move on to the next environment


    - submit pull request ;-)

    > The environments in question would be:
    >
    > - debian
    > - gentoo
    > - redhat


    I'm not sure gentoo is worth it. I doubt there still are users of these
    files.

    > We don't need to bother with:
    >
    > - fedora - superceded by redhat
    > - readynas ?????


    I've officially declared readynas support dead with LMS8. This support
    always ever covered the old 1st/2nd generation devices running Perl
    5.8/5.10, but none of the more recent (like... past 5 years) systems.

    > - solaris - still uses some kind of shell based init, right?


    I believe there are some community members who maintain solaris support
    in a different form, outside this repository.

  9. #29
    Senior Member
    Join Date
    May 2010
    Location
    London, UK
    Posts
    923
    Quote Originally Posted by scytale View Post
    Also it looks like at least in Debian it is fairly striaghtforward to use a postinst script to determine if systemd or sysVinit are in use an install the apropriate file:

    Check out this stackexchange answer
    These days, Debian, and the Debian package builder, has support for different init systems "built-in". So it should be equally straightforward to use the package builder's provided method instead a custom post-install script. Is there a reason why you don't suggest this approach ?

    I don't regularly maintain Debian packages, so any insight welcome.

    Quote Originally Posted by mherger View Post
    - submit pull request ;-)
    Which is what I was planning to do, for Debian only, after testing the service file that I originally suggested for a suitable period of time.

    Well, three months have passed and I have not experienced any issue on the few occasions I have started/stopped LMS in that time, and no-one else has reported any. I suppose some people may have tested .

    So, I guess the time has come. I'll await @scytales's input.

  10. #30
    Junior Member
    Join Date
    Aug 2014
    Posts
    8
    Quote Originally Posted by mrw View Post
    These days, Debian, and the Debian package builder, has support for different init systems "built-in". So it should be equally straightforward to use the package builder's provided method instead a custom post-install script.

    Is there a reason why you don't suggest this approach ?
    Nope I wasn't aware that that facility had been added

    Quote Originally Posted by mrw View Post
    I don't regularly maintain Debian packages, so any insight welcome.
    It's been several years since I worked with deb building myself.

    However the lms package looks quite trivial, and at a glance it looks like everything is handled by the buildme.sh script

    Quote Originally Posted by mrw View Post
    Which is what I was planning to do, for Debian only, after testing the service file that I originally suggested for a suitable period of time.

    Well, three months have passed and I have not experienced any issue on the few occasions I have started/stopped LMS in that time, and no-one else has reported any. I suppose some people may have tested .

    So, I guess the time has come. I'll await @scytales's input.
    Why don't you open a PR with what you've got (even if it's just the systemd unit file and nothing else) and we'll take it from there.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •