brew install libffi openssl
virtualenv -p /usr/bin/python2.7 blockstack-cli-venv
source blockstack-cli-venv/bin/activate
pip install --upgrade pip
pip install --upgrade blockstack
$ sudo pip install virtualenv
$ virtualenv /tmp/blockstack-install
$ cd /tmp/blockstack-install
$ source bin/activate
(blockstack-install) $ pip install blockstack
alias python=python3alias python=python2
I won't get into how much this is a bad idea; simply put, running
sudoin crontab requires your password to be stored somewhere in plaintext.
It's a bad idea.
The following is the preferred method of running administrative tasks through cron. Since you don't really need to write
sudo in the crontab, if you are modifying root's crontab.Use root's crontab
Run the following command:
This opens up
root's crontab. sudo is not necessary to run your command in this context, since it'll be invoked as root anyway.
Therefore, you would simply append the following to root's crontab.
Now, if you absolutely want to be unsafe and take risks with your password, the following will run your command from your own crontab, and enter your password automatically when prompted by
sudo.
Again, this is not recommended.
In your own crontab, write your command like so:
The obvious disadvantage here is that, should anyone ever access your crontab, your password will be readable in plaintext.
You shouldn't do this.
| |||
9
|
If you are putting the script from one of the cron directories (
/etc/cron.*) then you don't need to use sudo as that is running as root.
If you are using crontab, then you will want to use root's crontab. This will run it as root, and also not need sudo.
| ||||||||||||
|
-1
|
Run following command in terminal
Added the following line to the end of the file:
In the above example vidyadhar is the username and it will not ask for password if you are running rm command through vidyadhar.
|
$ setterm -blank 0 -powerdown 0
# echo -ne "\033[9;0]" >> /etc/issue
setterm -blank 0 on any shell to disable blanking out of tty consoles.0 disables blanking, any value greater than 0 is the time in minutes. Default is 10.~/.bashrc config.$ ls -l /dev/ttyUSB*(If this doesn't return any files, use "ls -l /dev/ttyS*" instead.)
crw-rw---- 1 root uucp 188, 0 Jul 22 02:49 /dev/ttyUSB0In this case the serial device is owned by user "root" and group "uucp", so you want to add yourself to the "uucp" group. In the examples below we will use "dialout" for the group we need to join.
$ sudo adduser (username) dialoutSubstitute your login name for (username)
$ groupswhich should respond with the full list of groups you belong to.
$ sudo users-adminsudo is used for all of these modifications to ensure that you have the correct read/write privilege for the files that will be changed. You must log out and log back in again for the change to take effect.
dmesgTorward the end of the messages, you should see this:
usb 1-1: new full speed USB device using uhci_and address 2 usb 1-1: configuration #1 chosen from 1 choiceNow, we need to figure out the device vendor number and product number to tell the usbserial driver. For this we can use lsusb. The easiest way to find the information is to first unplug the device, then run lsusb:
lsusbYou will see a summary list of your USB devices on the system, for example:
Bus 001 Device 001: ID 0000:0000Now, plug the device back in, and run lsusb again:
lsusbWhich returns the summary list again, but now showing the new USB device:
Bus 001 Device 002: ID 4348:5523 Bus 001 Device 001: ID 0000:0000Now, we can load up the driver for this device:
sudo modprobe usbserial vendor=0x4348 product=0x5523Finally, check dmesg again to ensure it loaded properly.
dmesgNear the end, you should see something like:
usbserial_generic 1-1:1.0: generic converter detected usb 1-1: generic converter now attached to ttyUSB0 usbcore: registered new interface driver usbserial_genericCongratulations, your link is up - in this example, the device can be used on /dev/ttyUSB0. As much fun as you had doing this, there is some chance you want to do this automatically in the future. Just add this line:
usbserial vendor=0x4348 product=0x5523to /etc/modules with the vendor and product numbers you found. Of course you must user sudo to edit that file.
vboxusers group. This can be done from Users and Groups after having installed the gnome-system-tools 
or from the command line bysudo usermod -aG vboxusers <username>
Note that we can only change these settings when the virtual machine is in shut down state.
Note, that some devices may lead to a boot failure of the guest. We can not use these devices for filters.
Name: ether1-gateway
MTU: 1500
L2 MTU: 1598
ARP: Enabled
VLAN
VLAN ID: 500
Name: vlan500
MTU: mtu1500
VLAN
VLAN ID: 600
Name: vlan600
MTU: mtu1500
Name: unifi
Type: PPPoE Client
Max MTU: 1492
Max MRU: 1492
Interfaces: vlan500
User: yourusername@unifi
Password: yourunifipassword
Name: bridge-iptv
Type: Bridge
MTU: 1500
Name: bridge-local
Type: Bridge
MTU: 1500
sudo visudo
username ALL=(ALL) NOPASSWD: ALL
nano (but note that the screenshot below shows vim), and it'll prompt you to save).
]sudo <Whatever you want>, without being prompted for the password.sudo command
in terminal window. For example, when you try to install a package in
software center, you will be prompted to insert your password, like you
can see in the next Screenshot.https://github.com/yagop/telegram-bot (written in LUA)
https://github.com/jh0ker/welcomebot (written in PYTHON)
https://github.com/yukuku/telebot (written in PYTHON)
sudo apt-get install python-pip
sudo python clibot.py
sudo python echobot2.py
pip3 install python-telegram-bot
sudo apt-get install python3-pip
python3 --version
Optional: sudo pip3 install -r requirements.txt
python3 -V
Optional: sudo pip3 install -r requirements-dev.txt
Optional: sudo make test
sudo python3 bot.py
sh -c "sh /home/administrator/Documents/masternode.sh"
#!bin/shsleep 15gnome-terminal --geometry=75x45 --title=Masternode --execute bash -c "sleep 5; cd ~; sudo ./dashd; sleep 60; sudo ./dashd getinfo ;bash"#gnome-terminal -e "cd ~ && sudo ./dashd"
root's user crontab instead of the systemwide crontab/etc/crontab? – Eliah Kagan Aug 10 '12 at 3:47