开发环境的定时启动脚本

开机启动并且定时运行

shell 的 jq 脚本真的是太难用了，调了半天才能用，文档看不懂。

完成的这个重启脚本非常有用：

cat nekoray.sh

#!/bin/bash
cd /opt/nekoray/config/profiles/;
port=`expr 0 + "6"$(date "+%m%d")`;
jq --indent 4 --argjson port "$port" '.bean.port |= $port'  0.json > tmp;
cp tmp 0.json;
ID=`ps -ef | grep nekoray | grep -v "$0" | grep -v "grep" | awk '{print $2}'`
echo $ID;
echo "---------------"
for id in $ID
do
kill -9 $id
echo "killed $id"
done
echo "---------------"
sleep 5;
nohup sh -c "PATH=/opt/nekoray:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin /opt/nekoray/nekoray" > /dev/null 2>&1 &
exit

以 root 的方式做重启：

cat startneko.sh

#!/bin/bash
echo "1"|sudo -S /home/uos/.script/nekoray.sh

自动更新配置的定时任务

sudo vim /etc/crontab

0  0    * * *   root    /home/uos/.script/nekoray.sh

sudo systemctl restart cron

现在就做到无感知的定时重启了。

开机启动的方法

sudo ln -s ~/.script/startneko.sh /etc/profile.d/

这个 qt 程序的开机自起一直有 xcb 的报错，不弄了。用 nekoup 写个 alias 非常地好用。

发现了一个好办法

vim ~/.config/autostart/nekoray.desktop

[Desktop Entry]
Type=Application
Exec=/home/uos/.script/startneko.sh
Hidden=false
NoDisplay=false
X-GNOME-Autostart-enabled=true
Name=Nekoray

chmod +x nekoray.desktop

亲测可用，这样开机启动是没有问题了。并且确实是以 root 权限做的启动。qt-gui 的程序估计是不能用 daemon 的方式运行的。qt-core 的程序才能以 root 的方式运行。

关闭 ubuntu 的错误报告

永久关闭。 sudo gedit /etc/default/apport 修改 enabled=0 ，重启生效

启用代理和关闭代理的脚本

如果不是用的 tun 模式的话而是用的代理模式，那么上面只解决了一部分协议的问题，后面可以参考这个项目做一个一键切换的脚本。

setProxy: https://github.com/dabrign/setProxy

simple bash script to set and remove proxy from the command line

Supported services
- Bash
- Apt in /etc/apt/apt.conf Acquire::http::Proxy “http://%7B%7Buser%7D%7D:%7B%7Bpasword%7D%7D@{{proxyurl:port}}” ;
- Gnome
Other needed services
- NPM
npm config set proxy http://proxy.company.com:8080 npm config set https-proxy http://proxy.company.com:8080 npm config delete proxy npm config delete https-proxy
- PIP & CONDA
Env var works for pip
- GIT
git config –global http.proxy {{url}} git config –global https.proxy {{url}} git config –global –unset https.proxy git config –global –unset http.proxy
- docker File
http-proxy.conf in /etc/systemd/system/docker.service.d with: [Service] Environment=“HTTP_PROXY= "
- maven .m2/settings

#!/bin/bash
HTTP_PROXY="export http_proxy"
HTTPS_PROXY="export https_proxy"
FTP_PROXY="export ftp_proxy"
APTCONF="/etc/apt/apt.conf"
if grep -Fxq "$HTTP_PROXY" ~/.bashrc
then
    echo "Already set"
        read -r -p "do you wanna remove? [y/n]" response
        if [[ $response =~ ^([yY][eE][sS]|[yY])$ ]]
        then
                sed -i '/no_proxy/d' ~/.bashrc
                sed -i '/http_proxy/d' ~/.bashrc
                sed -i '/https_proxy/d' ~/.bashrc
                sed -i '/ftp_proxy/d' ~/.bashrc
                sudo sed -i '/Acquire::http::Proxy/d' $APTCONF
                gsettings set org.gnome.system.proxy mode 'none'
        else
        echo "ok, no exception then!"
        fi
else
        gsettings set org.gnome.system.proxy mode 'manual'
    echo "you can set it now"
        read -r -p "Set your proxy in form http://user:pwd@proxy:port : " response
        echo "http_proxy=$response" >> ~/.bashrc
        echo "https_proxy=$response" >> ~/.bashrc
        echo "ftp_proxy=$response" >> ~/.bashrc
        echo "export http_proxy" >> ~/.bashrc
        echo "export https_proxy" >> ~/.bashrc
        echo "export ftp_proxy" >> ~/.bashrc
        if [ -f $APTCONF ];
        then
                echo "appending"
        else
                echo "creating..."
                sudo touch $APTCONF

        fi
        sudo sh -c " echo 'Acquire::http::Proxy \"$response\" ;' >> $APTCONF"

        read -r -p "do you wanna add exceptions? [y/n]" response
        if [[ $response =~ ^([yY][eE][sS]|[yY])$ ]]
        then
        read -r -p "Set your proxy exceptions in form ip_add,host1,host2" response
                echo "no_proxy=$response" >> ~/.bashrc
                echo "export no_proxy" >> ~/.bashrc
        else
        echo "ok, no exception then!"
        fi
        source ~/.bashrc
fi