1. Forum
  2. Usenet
  3. COMP.OS.LINUX.SETUP

  • [OT] Any chance to avoid GPT?

    From Bit Twister@21:1/5 to The Natural Philosopher on Sat Sep 16 17:40:29 2017
    On Sat, 16 Sep 2017 11:45:38 +0100, The Natural Philosopher wrote:

    * worst problem was NFS mintes hard coded into /etc./fstab didnt work as
    the mounting seemd to fail beforer wifi got going. Couyld be a mint 18/systemd thing?

    Hehehe, not sure about NFS, but more like your distribution not
    configuring the NFS systemd service to wait for the network going
    active before starting NFS.

    You could create your own chopped down service file to not attempt to
    start NFS until the network online target is running.

    For example, I want as clean as possible journal because I have a hourly
    cron job checking the journal for problems. Noticed mysqld bitching
    about unable to call home until the network was up.

    Simple solution was to create my own
    /etc/systemd/system/mysqld.service.d/ service file to tell systemd
    to wait until network was up. I also wanted to reduce the fail
    timeout value. Resulting fix for my Mageia Linux setup:


    $ cat /etc/systemd/system/mysqld.service.d/xx__local.conf
    #
    # Created by /local/bin/mysqld_service_changes Thu 10 Aug 13:18 2017
    #

    [Unit]
    After=network-online.target

    [Service]
    # Give a reasonable amount of time for the server to start up/shut down TimeoutSec=150

    #*********** end of /etc/systemd/system/mysqld.service.d/xx__local.conf *****

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From The Natural Philosopher@21:1/5 to Bit Twister on Sun Sep 17 11:39:45 2017
    On 16/09/17 18:40, Bit Twister wrote:
    On Sat, 16 Sep 2017 11:45:38 +0100, The Natural Philosopher wrote:

    * worst problem was NFS mintes hard coded into /etc./fstab didnt work as
    the mounting seemd to fail beforer wifi got going. Couyld be a mint
    18/systemd thing?

    Hehehe, not sure about NFS, but more like your distribution not
    configuring the NFS systemd service to wait for the network going
    active before starting NFS.

    Probably. sytemd is bound to be at the bottom of it



    You could create your own chopped down service file to not attempt to
    start NFS until the network online target is running.

    For example, I want as clean as possible journal because I have a hourly
    cron job checking the journal for problems. Noticed mysqld bitching
    about unable to call home until the network was up.

    Simple solution was to create my own
    /etc/systemd/system/mysqld.service.d/ service file to tell systemd
    to wait until network was up. I also wanted to reduce the fail
    timeout value. Resulting fix for my Mageia Linux setup:


    $ cat /etc/systemd/system/mysqld.service.d/xx__local.conf
    #
    # Created by /local/bin/mysqld_service_changes Thu 10 Aug 13:18 2017
    #

    [Unit]
    After=network-online.target

    [Service]
    # Give a reasonable amount of time for the server to start up/shut down TimeoutSec=150

    #*********** end of /etc/systemd/system/mysqld.service.d/xx__local.conf *****


    I could, but I never needed to before. I will wait till the bug gets fixed.

    Frankly Mint 17.3 is good enough for me,. and I have noted a large
    amount of 'updates' actually are worse than what they replaced.

    Programmers should not try to reinvent the wheel every year, just fix
    the bugs and improve the speed and security



    --
    "Nature does not give up the winter because people dislike the cold."

    ― Confucius

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)