![]() ![]() NOTE: If you've used cron then are aware that crontab entries are run in a restricted environment - the same applies to systemd: always use absolute paths, and make no assumptions of any variables being defined. To save you extra typing you can add in your ~/.bashrc the line alias sc='sudo systemctl $*' then you'll be able to shorten the commands above to e.g. Start the service: sudo systemctl start tgĭisable the service: sudo systemctl disable tg Now you can enable the service to autostart: sudo systemctl enable tg ĮxecStart=/usr/local/bin/telegram-cli -k /etc/telegram-cli/tg-server.pub -W -P 1234 -d -vvvRC Place it in /etc/systemd/system/tg.service. It contains a lot of uncensored videos, including shocking real-life content, extreme content, age-restricted content, etc. Kaotic Kaotic could be the website most like LiveLeak. The following are 11 best alternative sites to LiveLeak. you can set your service to start after the network is up ( Wants=network-online.target in the section).Īn example service that starts a telegram-cli daemon. Fortunately, for regular visitors of LiveLeak, there are still some sites like LiveLeak. Establish startup preconditions and dependencies, i.e.Setting the service type: Type=simple|forking|oneshot|notify|dbus.Restart services on failure with configurable timeouts: Restart=on-failure|on-watchdog|on-abnormal|always.I'll summarize some benefits ( systemd can do a lot more): Systemd has become ubiquitous in many modern distros, and it offers a lot of control and flexibility in terms of how your services are started and how they run. If the thing you want to autostart is not a graphical app which requires a desktop then it's best to avoid using any autostart facilities provided by xorg or by your current desktop environment. But a better approach to running post-connect scripts might be systemd (for systems that support it, which is the majority of modern distros). If the network is configured via ifupdown, then post-up scripts can be placed in the /etc/network/if-up.d/ folder. Both NetworkManager and wicd have their own ways of specifying post-connect autorun entries. In that case you should check the special post-connect scripts that can be defined for your network manager. ![]() It is a bit different if you need to run your scripts after the network is up and running. įor LXDE autostart entries can also be set in ~/.config/lxsession/LXDE/autostart. etc/xdg/autostart is for system-wide configuration. config/autostart is supposed to be a desktop-neutral way of defining autorun entries. Apart from system-level startup scripts your desktop environment might have its own way of auto-running programs. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |