• Recent
  • Tags
  • Popular
  • Search
  • ads.txt
Collapse
Lime-it.us

Force crontab editor :: default editor

Scheduled Pinned Locked Moved Linux Systems Guides
defaultcrontabnanoeditor
1 Posts 1 Posters 941 Views
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • rickR Offline
    rickR Offline
    rick
    wrote on last edited by rick
    #1

    Many times you type:

    crontab -e
    

    And end up with key bindings your not used to. (h,j,k,i) As in vi or ed.

    Say you normally use nano:

    export VISUAL=nano; crontab -e
    

    Boom, crontab will open and nano will be your editor.


    Same goes for vi:

    export VISUAL=vim; crontab -e
    

    Then again maybe you want to use your preferred editor always, or as default.

    Get a list of available editors currently install on your system by running:

    update-alternatives --list editor
    

    In this case, the output is:

    /bin/ed
    /bin/nano
    /usr/bin/vim.gnome
    /usr/bin/vim.tiny
    

    So you may combine the above for on demand usage such as:

    export VISUAL=ed; crontab -e
    

    Or:

    export VISUAL=vim.gnome; crontab -e
    

    ect…


    To make one specific editor default to your users profile, you must edit:

    ~/.profile
    

    So for example if your enjoying the ease of nano:

    nano ~/.profile
    

    And add these lines as follows:

    EDITOR=nano
    VISUAL=$EDITOR
    export EDITOR VISUAL
    

    Replacing in the above case ‘nano’ with your desired default editor.


    When you run the following as root, you are changing the default editor system wide, or all users. In this case, we can use ‘editor’, to see which editors are currently available on the system, as well as priorities, paths, and status:

    update-alternatives --config editor
    

    The output will be:

      Selection    Path                Priority   Status
    ------------------------------------------------------------
    * 0            /usr/bin/vim.gnome   60        auto mode
      1            /bin/ed             -100       manual mode
      2            /bin/nano            40        manual mode
      3            /usr/bin/vim.gnome   60        manual mode
      4            /usr/bin/vim.tiny    10        manual mode
    Press enter to keep the current choice[*], or type selection number: 
    

    Then simply type the number of the default system wide editor you wish.

    1 Reply Last reply
    0
    • rickR

      Basic file permissions

      Scheduled Pinned Locked Moved Linux Systems Guides permissions
      1
      0 Votes
      1 Posts
      47 Views
      No one has replied
    • rickR

      Install locate *nix

      Scheduled Pinned Locked Moved Linux Systems Guides locate
      1
      0 Votes
      1 Posts
      66 Views
      No one has replied
    • rickR

      Set script to executable

      Scheduled Pinned Locked Moved Linux Systems Guides chmod terminal executable
      1
      +0
      0 Votes
      1 Posts
      48 Views
      No one has replied
    • rickR

      Only one CPU is allowed in this system

      Scheduled Pinned Locked Moved Linux Systems Guides trruenas one cpu allowed
      1
      +0
      0 Votes
      1 Posts
      102 Views
      No one has replied
    • rickR

      Ubiquity AP-Pro LED replacement

      Scheduled Pinned Locked Moved Linux Systems Guides ubiquity unify ap-pro udm-se pfsense led
      1
      0 Votes
      1 Posts
      259 Views
      No one has replied
    • rickR

      Setting a cron

      Scheduled Pinned Locked Moved Linux Systems Guides crontab export editor cron
      1
      +0
      0 Votes
      1 Posts
      566 Views
      No one has replied
    • rickR

      Reset NodeBB admin password

      Scheduled Pinned Locked Moved Linux Systems Guides lost admin pass reset password nodebb admin
      1
      0 Votes
      1 Posts
      1k Views
      No one has replied
    • rickR

      Deleting files - delete directory

      Scheduled Pinned Locked Moved Linux Systems Guides
      1
      0 Votes
      1 Posts
      1k Views
      No one has replied

  • rickR

    Re: Set script to executable

    755 - Owner has all permissions, and Group and Other can read and execute 700 - Owner has all permissions 644 - Owner can read and write, and Group and Other can read 600 - Owner can read and write 775 - Owner can read and write, and Group and Other can read 770 - Owner and Group have all, and Other can read and execute 750 - Owner has all permissions, and Group can read and execute 664 - Owner and Group can read and write, and Other can just read 660 - Owner and Group can read and write 640 - Owner can read and write, and Group can read
    • read more

  • rickR

    Re: Find or Locate a file or extension command line

    Install locate command linux: Use your sudo command!

    apt install mlocate

    OR:

    apt-get install mlocate

    OR:

    yum install mlocate

    Update the database:

    updatedb

    Depending on the size of the complete filesystem this could take a few minutes

    After the database has been populated:

    locate mariadb

    Where mariadb is the word your looking for

    • read more

  • rickR

    These commands are if you are in the scripts directory! Changing permissions can be done from anywhere in the structure.

    Such as :

    chmod +x /opt/so-elastic-agent_linux_amd64

    Terminal chmod to executable :

    Permissions prior to chmod : chmod.png

    chmod +x so-elastic-agent_linux_amd64

    Permissions following chmod : chmod-x.png

    Then execute :

    ./so-elastic-agent_linux_amd64

    Insure you are acting as the user you just gave permissions to (the file owner) or at least have sudo privileges

    To make the script un-executable:

    chmod -x so-elastic-agent_linux_amd64
    • read more

  • rickR
    sudo apt install lsb-release ca-certificates curl -y

    GPG key and repo for php 7.4

    sudo curl -sSLo /usr/share/keyrings/deb.sury.org-php.gpg https://packages.sury.org/php/apt.gpg sudo sh -c 'echo "deb [signed-by=/usr/share/keyrings/deb.sury.org-php.gpg] https://packages.sury.org/php/ $(lsb_release -sc) main" > /etc/apt/sources.list.d/php.list'

    Update the system with the new repository in place

    sudo apt update

    Install the dependencies for OwnCloud (LAMP ect) Certbot, or LetsEncrypt is being installed as well, if you are using this installation in a public domain

    sudo apt install apache2 mariadb-server imagemagick certbot python3-certbot-apache smbclient redis-server unzip rsync libapache2-mod-php7.4 php7.4 php7.4-intl php7.4-mysql php7.4-mbstring php7.4-imagick php7.4-igbinary php7.4-gmp php7.4-bcmath php7.4-curl php7.4-gd php7.4-zip php7.4-imap php7.4-ldap php7.4-bz2 php7.4-ssh2 php7.4-common php7.4-json php7.4-xml php7.4-dev php7.4-apcu php7.4-redis libsmbclient-dev php-pear php-phpseclib

    Enable apache2 and then verify it’s status

    sudo systemctl is-enabled apache2 sudo systemctl status apache2

    oc-apache.png Enable MariaDB and verify status

    sudo systemctl is-enabled mariadb sudo systemctl status mariadb

    oc-maria.png Enable Redis and verify status

    sudo systemctl is-enabled redis sudo systemctl status redis

    oc-redis.png

    Configure default php version

    sudo update-alternatives --config php

    oc-php-alternatives.png oc-php-ver.png

    Configure php OwnCloud dependencies

    sudo update-alternatives --set phar /usr/bin/phar7.4 sudo update-alternatives --set phar.phar /usr/bin/phar.phar7.4 sudo update-alternatives --set phpize /usr/bin/phpize7.4 sudo update-alternatives --set php-config /usr/bin/php-config7.4

    Upgrade Pear to OwnCloud4 requirements

    sudo mkdir -p /tmp/pear/cache sudo pear upgrade --force --alldeps http://pear.php.net/get/PEAR-1.10.13

    oc-pear-up.png

    sudo pear clear-cache sudo pear update-channels sudo pear upgrade --force sudo pear upgrade-all

    Verify Pear version

    pear version

    oc-pear-ver.png

    Configure MariaDB

    sudo mariadb-secure-installation

    oc-mariadb-setup.png

    Log into MariaDB

    sudo mariadb -u root -p

    Create the OwnCloud database:

    This is where many go wrong, we do not use ‘password’ we replace password, with our own password.

    CREATE DATABASE owncloud;

    We just created a database with the name owncloud

    CREATE USER IF NOT EXISTS 'owncloud'@'localhost' IDENTIFIED BY 'password';

    We just created a database user called owncloud

    GRANT ALL PRIVILEGES ON owncloud.* TO 'owncloud'@'localhost' WITH GRANT OPTION;

    We just allowed user owncloud, full privileges on database owncloud

    FLUSH PRIVILEGES;

    Now verify what we have just done:

    SHOW GRANTS FOR 'owncloud'@'localhost';

    You can see below I named this database ‘oc’ and the ‘oc’ user has privileges on database ‘owncloud’

    oc-db-priv.png

    quit;

    wget the OwnCloud source

    cd /var/www wget https://download.owncloud.com/server/stable/owncloud-complete-latest.tar.bz2

    Grab sha256 to verify the download

    wget https://download.owncloud.com/server/stable/owncloud-complete-latest.tar.bz2.sha256

    BEFORE installing, verify if the download of OwnCloud matches what the OwnCloud team wanted you to have, this is important always.

    sudo sha256sum -c owncloud-complete-latest.tar.bz2.sha256 < owncloud-complete-latest.tar.bz2

    Out put should say ‘OK’ if everything matches.

    Change ownership of the directory to www-data user.

    sudo chown -R www-data:www-data /var/www/owncloud

    Configure Vhost for OwnCloud

    This will open a new file in 'sites-available and name this file ‘owncloud.conf’

    Change the ServerName and ServerAlias, as well as log file names, to whatever your domain is. There are many ways to do this keep in mind.

    sudo nano /etc/apache2/sites-available/owncloud.conf <VirtualHost *:80> ServerName oc ServerAlias www.oc DocumentRoot /var/www/owncloud ErrorLog ${APACHE_LOG_DIR}/oc.io-error.log CustomLog ${APACHE_LOG_DIR}/oc.io-access.log combined Alias /owncloud "/var/www/owncloud/" <Directory /var/www/owncloud/> Options +FollowSymlinks AllowOverride All <IfModule mod_dav.c> Dav off </IfModule> SetEnv HOME /var/www/owncloud SetEnv HTTP_HOME /var/www/owncloud </Directory> </VirtualHost>

    Enable and verify the owncloud vhost

    sudo a2ensite owncloud.conf sudo apachectl configtest

    oc-apache.png

    Now install OwnCloud

    Change the database name, user, and password to whatever you named the OwnCloud database earlier;

    Change the ‘admin user’ and ‘admin pass’ to whatever you want the new OwnCloud admin account to be.

    sudo -u www-data /var/www/owncloud/occ maintenance:install \ --database "mysql" \ --database-name "owncloud" \ --database-user "owncloud"\ --database-pass "password" \ --admin-user "admin" \ --admin-pass "your new owncloud admin password"

    Edit the OwnCloud config file to add the domain you used earlier in the Apache2 vhost file:

    sudo nano /var/www/owncloud/config/config.php 'trusted_domains' => array ( 0 => 'localhost', 1 => 'whatever your domain is goes here', ),

    Personally I restart the server at this point, which will restart all services. Then visit the domain / IP of your settings and you should see the OwnCloud login page. Use the credentials you setup for the admin user.

    System cron setting:

    sudo crontab -u www-data -e */15 * * * * /usr/bin/php -f /var/www/owncloud/occ system:cron

    Memcache with Redis we installed earlier:

    sudo nano /var/www/owncloud/config/config.php 'filelocking.enabled' => true, 'memcache.local' => '\OC\Memcache\APCu', 'memcache.locking' => '\OC\Memcache\Redis', 'redis' => [ 'host' => 'localhost', 'port' => 6379, ],

    Go restart the server again and enjoy!

    • read more

  • rickR

    Comment out in=>

    /usr/lib/python3/dist-packages/middlewared/plugins/vm/vms.py # elif flags['intel_vmx']: # if vcpus > 1 and flags['unrestricted_guest'] is False: # verrors.add(f'{schema_name}.vcpus', 'Only one Virtual CPU is allowed in this system.') # elif flags['amd_rvi']: # if vcpus > 1 and flags['amd_asids'] is False: # verrors.add( # f'{schema_name}.vcpus', 'Only one virtual CPU is allowed in this system.' # )

    At this point we must comment out each time we update the system.

    • read more

  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Recent
  • Tags
  • Popular
  • Search
  • ads.txt