1. Install postfix and configure as Internet site.
2. Enter Gmail details in 2 files: /etc/postfix/main.cf and /etc/postfix/sasl_passwd:
$ sudo postmap /etc/postfix/sasl/sasl_passwd
This should create /etc/postfix/sasl/sasl_passwd.db
relayhost = [smtp.gmail.com]:587
smtp_use_tls = yes
smtp_sasl_auth_enable = yes
smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd
smtp_tls_CAfile = /etc/ssl/certs/ca-certificates.crt
# These two additional settings only used if using port 465
#smtp_tls_wrappermode = yes
#smtp_tls_security_level = encrypt
recipient_delimiter = +
mailbox_size_limit = 0
$ sudo systemctl restart postfix
The user’s full name who sends emails will show as the sender, so setting the full name to something like email@example.com can be helpful to quickly identify the origin of an automated email, in case you receive them from different servers.
To edit a user’s full name:
usermod -c "firstname.lastname@example.org" john
Having multiple users with directories set with non-readable files and directories is a problem when backing up data via ssh to or from a remote server. This is because the remote backup user cannot read all files and directories in the local system and the local root user cannot write to the sshfs mount or scp to the remote backup server – because I configure my servers to reject root login.
Therefore, it is necessary to use access control lists (ACL) to allow a remote backup user to have full read-only permission on SSH/NFS mounted filesystems that need to be backed up.
To accomplish this, after creating a local backup user, set read-only permissions on the desired directory:
sudo setfacl -m u:backup:r-X -R /data
-R applies the r-X attribute recursively to user “backup” in the local system.
To check the ACL, use:
In the remote backup system, create a backup user who can ssh into the system to be backed up.
Use sshfs to mount /data/ in the remote system. The ACL will allow the backup user to read all files and directories.
One caveat is that it is necessary to issue the setfacl command every time before backing up. If a user sets chmod 700 or chmod 600 in a file or directory, that directory or file will become unreadable by the backup user. So it’s important to set the read permission to the backup user every time to make sure everything is readable during backup.
I keep forgetting how to upload a directory recursively using the Linux sftp command line program.
The trick is to manually create the target directory in the sftp server then do put -r .
Example, to recursively upload the local directory “test” that contains subdirectories and files:
sftp> mkdir test
sftp> put -r test
I have two webservers that have no GUI and are managed remotely via ssh.
In order to synchronize data across the two servers in “real time”, I opted for syncthing. However, syncthing configuration is done on a web browser GUI which isn’t installed in my servers.
The way I found to have access to the GUI of each server was to create an ssh tunnel and tunnel my local web browser traffic into the remote servers:
ssh -L 12341:localhost:8384 webserver1
ssh -L 12342:localhost:8384 webserver2
This commands will allow you to tunnel traffic from localhost port 12341 into webserver1 port 8384 (and vice-versa) and from localhost port 12342 into webserver2 port 8384 (and vice-versa). In other words, when you point your browser to localhost:12341 in your local computer, it will connect to webserver1:8384 and localhost:12342 will connect o webserver2:8384.
Use the command below to connect to an sftp server using ssh, no password and an RSA key as authentication method.
lftp -u sftpuser, sftp://myserver.com/ -e 'set sftp:connect-program
"ssh -p [PORT] -i [path/id_rsa] " '
After I had to kill RStudio because the process it was running ate all the temporary space, RStudio would freeze when trying to open an R script.
In addition, when running a third party R function, I got this strange error saying it couldn’t change directory.
The fix was deleting this file:
There is a lot of information available regarding installation of single-boot Ubuntu on an Acer C720P but here I’m posting what works for me in Jan 2017.
I am not going to explain how to prepare the Chromebook for installation of Ubuntu, I’m just posting notes on certain configurations that work for me:
Basic hardware functionality
- Elantech touchpad: the newest kernels recognize the touchpad perfectly (>= 4.8). Previously, only the GalliumOS kernel made the touchpad usable for me.
- Download the amd64 kernel from here and install: http://kernel.ubuntu.com/~kernel-ppa/mainline/
- For example, for 4.9, you need to download
- Install using dpkg -i linux-*.deb
- Touchscreen: works with any kernel.
- Microphone: does not work
- Speakers: work with any kernel
Enabling keyboard functions and keys
- Install programs to control brightness and map keys:
- apt-get install xbindkeys xdotool xbacklight
- create ~/.xbindkeysrc with these contents to map keys (customize to your needs)
"xdotool keyup F1; xdotool key alt+Left"
"xdotool keyup F2; xdotool key alt+Right"
"xdotool keyup F3; xdotool key ctrl+r"
"xdotool keyup F4; xdotool key F11"
"xdotool keyup F5; gnome-screenshot -f $HOME/Pictures/Screenshot_$(date +%F_%T).png"
"xdotool keyup F6; xbacklight -dec 3"
"xdotool keyup F7; xbacklight -inc 3"
"xdotool keyup F8; pactl set-sink-mute alsa_output.pci-0000_00_1b.0.analog-stereo toggle"
#"xdotool keyup F9; pactl set-sink-volume alsa_output.pci-0000_00_1b.0.analog-stereo -10%"
"xdotool keyup F9; amixer -D pulse sset Master 5%-"
#"xdotool keyup F10; pactl set-sink-volume alsa_output.pci-0000_00_1b.0.analog-stereo +10%"
"xdotool keyup F10; amixer -D pulse sset Master 5%+"
"xdotool keyup control+shift+Down Arrow; xdotool key Page_Down; xdotool keydown shift"
"xdotool keyup control+shift+Up Arrow; xdotool key Page_Up"
"xdotool keyup control+shift+Left Arrow; xdotool key Home"
"xdotool keyup control+shift+Right Arrow; xdotool key End"
"xdotool keyup XF86PowerOff; xdotool key Delete"
- Notice that I disable the power button and map it to Del. To shutdown the computer, I use the shutdown button in Gnome panel.
Using a lightweight Desktop (Openbox):
- Even Gnome 2 uses too much memory for my likings. Openbox uses < 350 MB idle and Gnome ~ 600 MB idle. 250 MB in a 2 GB system is a lot for me. With Openbox I get a light Gnome-like desktop.
- Install Openbox:
sudo apt-get install openbox
- Install gnome-session-fallback:
sudo apt-get install gnome-session-fallback
- I use some Gnome applications.
- Also, Chromebooks don’t have a “Super” key, which is required in Openbox to add buttons to gnome-panel. In Gnome, you can add buttons by clicking the right mouse button and Alt only. So I login to Gnome, configure gnome-panel, logout and login to Openbox.
- Alternatively, plug in a keyboard and click Super+Alt and the right mouse key on the Gnome panel in Openbox to add items). But this means you always depend on an external keyboard to configure Gnome panel in Openbox.
- Install volti to control the sound volume. Gnome’s won’t work:
sudo apt-get install volti
- Configure gnome-panel. The native Gnome indicator applet won’t work in Openbox, which means no network manager, no clock, etc.To configure Gnome panel in Openbox without plugging an external keyboard: login to Gnome (metacity) and configure the gnome-panel with the mouse, adding:
- A custom application launcher that will be the shutdown button. Select a shutdown icon to be displayed.
- Create this script and configure the shutdown button in Gnome panel to call this script:
gmessage "Are you sure you want to shut down your computer?" -center -title "Take action" -font "Sans bold 10" -default "Cancel" -buttons "_Cancel":1,"_Log out":2,"_Reboot":3,"_Shut down":4,"_Suspend":5 >/dev/null
case $? in
shutdown -r now;;
shutdown -h now;;
- Remove the bottom panel bar for more screen real estate.
- Add a window selector to the top panel bar.
- Add desired application shortcuts.
- Add a clock.
- Logout from Gnome and login to Openbox.
- In a terminal, create .config/openbox/autostart.sh
- Install gxmessage to show the shutdown dialog when you press the shutdown button:
apt-get install gxmessage
- Configure sudoers to allow any user to shutdown:
- sudo visudo
- Insert this at the end of the file:
%users ALL=NOPASSWD: /usr/bin/shutdown
- I’m still working on how to make pm-suspend work without sudo.
- Configure start up applications: Edit .config/openbox/autostart.sh to start several applications upon login:
gnome-panel & # openbox has no panels, you need to start one
volti & # sound control
nm-applet & # for network management
xbindkeys # for key mapping to the weird Chromebook keyboard
synclient ClickFinger3=2 # to enable right click on the touchpad (tap the touchpad with 2 fingers simultaneously)
synclient TapButton3=2 # to enable pasting with the touchpad (tap the touchpad with 3 fingers simultaneously)
earlyoom # aggressively kill programs when there's no RAM available, see below
- Enable a screensaver:
- gnome-screensaver doesn’t work.
- Install xscreensaver instead and remove gnome-screensaver:
sudo apt-get remove gnome-screensaver
sudo apt-get install xscreensaver
- run xscreensaver-demo to configure the screensaver.
- Backup .config/ so anytime you have to reinstall you don’t need to reconfigure Gnome panel and start up applications.
- SSD settings: configure /etc/fstab with configurations that are more gentle on your SSD: Add discard,noatime,errors=remount-ro to /dev/sda1:
/dev/sda1 / ext4 discard,noatime,errors=remount-ro 0 1
- Swap: I used to disable swap completely and let programs crash if they used too much memory. However, there seems to be a bug in 16.04 and sometimes kswapd0 runs at 100% CPU for several minutes when there’s not swap. So now I:
- create a very small swap (10 MB)
- decrease swappiness (sudo sysctl vm.swappiness=10)
- use earlyoom (https://github.com/rfjakob/earlyoom) to aggressively kill programs. I add it to .config/openbox/autostart