To install tcptraceroute on Debian/Ubuntu:
$ sudo apt-get install tcptraceroute
To install tcptraceroute on CentOS/REHL, first set up RepoForge on your system, and then:
$ sudo yum install tcptraceroute
To install tcptraceroute on Debian/Ubuntu:
$ sudo apt-get install tcptraceroute
To install tcptraceroute on CentOS/REHL, first set up RepoForge on your system, and then:
$ sudo yum install tcptraceroute
/* file:///Users/henryhuman/Documents/04_Business/Bootstrap%20Creative/GitHub%20repositories/bootstrap-classes-list/bootstrap4.5.0.html */ | |
.accordion | |
.active | |
.alert | |
.alert-danger | |
.alert-dark | |
.alert-dismissible | |
.alert-heading | |
.alert-info |
The connection failed because by default psql
connects over UNIX sockets using peer
authentication, that requires the current UNIX user to have the same user name as psql
. So you will have to create the UNIX user postgres
and then login as postgres
or use sudo -u postgres psql database-name
for accessing the database (and psql
should not ask for a password).
If you cannot or do not want to create the UNIX user, like if you just want to connect to your database for ad hoc queries, forcing a socket connection using psql --host=localhost --dbname=database-name --username=postgres
(as pointed out by @meyerson answer) will solve your immediate problem.
But if you intend to force password authentication over Unix sockets instead of the peer method, try changing the following pg_hba.conf
* line:
from
$(function() { | |
var topoffset = 70; //variable for menu height | |
//Use smooth scrolling when clicking on navigation | |
$('.navbar-nav a').click(function() { | |
if (location.pathname.replace(/^\//,'') === | |
this.pathname.replace(/^\//,'') && | |
location.hostname === this.hostname) { | |
var target = $(this.hash); | |
target = target.length ? target : $('[name=' + this.hash.slice(1) +']'); |
Do you need a refresher on git? Go through Codecademy's git
course.
Using your terminal/command line, get inside the folder where your project files are kept:
cd /path/to/my/codebase
.
→ You cannot do this simply by opening the folder normally, you must do this with the command line/terminal.
→ Do you need a refresher on using your command line/terminal? I've compiled my favorite resources here.
Check if git is already initialized: git status
In /usr/share/pulseaudio/alsa-mixer/paths/analog-input-internal-mic.conf
and /usr/share/pulseaudio/alsa-mixer/paths/analog-input-mic.conf
:
[Element Internal Mic Boost]
set volume to zero
.[Element Int Mic Boost]
set volume to zero
.[Element Mic Boost]
set volume
to zero
Find your source name from the following command; mine is alsa_input.pci-0000_00_1f.3.analog-stereo
$ pacmd list-sources | grep 'name:.*input'
Edit /etc/pulse/default.pa
and add the following lines, where INPUT_NAME
is name of the input source from above step:
In a short note, YAML files represent configuration data in most of the times. According to Wikipedia: YAML "is a human-friendly data serialization standard for all programming languages". Basically we can say that is similar to XML and JSON notation and it is pretty used on DevOps activities for IaC configurations and for sharing data across multiple applications.
key-Value Pair: there's nothing more to say to this. You have a "Key" that acts as an Identification for value itself.
Here's an example: