PGTune calculate configuration for PostgreSQL based on the maximum performance for a given hardware configuration. It isn’t a silver bullet for the optimization settings of PostgreSQL. Many settings depend not only on the hardware configuration, but also on the size of the database, the number of clients and the complexity of queries, so that optimally configure the database can only be given all these parameters.

ldapsearch -x -b 'dc=southpolecarbon,dc=com' -D 'cn=admin,dc=southpolecarbon,dc=com' '(uid=pweber)' -W -LLL

ldapadd -x -D 'cn=admin,dc=southpolecarbon,dc=com' -W -f adduser.ldif

dn: uid=atesto,ou=people,dc=southpolecarbon,dc=com
objectClass: inetOrgPerson
objectClass: shadowAccount
objectClass: posixAccount
sn: Testo
givenName: Alfonso
description: Alfonso Testo
shadowLastChange: 0
shadowWarning: 14
gidNumber: 10000
gecos: Patrick Weber
uid: atesto
homeDirectory: /home/samba-user-home/atesto
loginShell: /bin/false
cn: Alfonso Testo
uidNumber: 20000
displayName: Alfonso Test
userPassword:: efjlkajfdsafjösfjökafödfjalfjdl
title: Project Developper
telephoneNumber: +41 078 662 59 55
l: Zurich
businessCategory: Projects

change loglevel

cd /root/
ldapmodify -Y external -H ldapi:/// -D 'cn=config' -f loglevel64.ldif
ldapmodify -Y external -H ldapi:/// -D 'cn=config' -f loglevel0.ldif

Die aktuelle Einstellung kann man so sehen:
ldapsearch -LLL -Q -Y EXTERNAL -H ldapi:/// -b cn=config  olcLoglevel

mysql -u sugaruser -p
use sugarcrm_prod;

truncate contacts;
truncate contacts_audit;
truncate contacts_bugs;
truncate contacts_cases;
truncate contacts_cstm;
truncate contacts_users;

truncate leads;
truncate leads_audit;
truncate leads_cstm;

truncate opportunities;
truncate opportunities_audit;
truncate opportunities_contacts;
truncate opportunities_cstm;

truncate accounts;
truncate accounts_audit;
truncate accounts_cstm;

first app

sudo apt install git
sudo apt install mongod
sudo apt install mongodb
mongod --version
sudo systemctl status mongodb
sudo apt install nginx 
sudo apt install nodejs npm 
node -v 
mkdir first
cd first 
npm init 
npm install express --save
var express = require('express');
var app = express();

app.get('/', function (req, res) {
  res.send('Hello World!');

app.listen(3000, function () {
  console.log('Example app listening on port 3000!');

location ~ \.php { proxy_pass; }
node app.js

SQL Syntax Check Online, SQL Validator, Instant SQL Compiler Online

 `accounts_cstm` ca,
 accounts_contacts ac,
 accounts a,
 contacts c,
 email_addr_bean_rel b,
 email_addresses e
 ca.reportingto_c = '^CDP^'
 OR ca.commitments_c IN ('^Science based targets^', '^TCFD^', '^RE100^')
 AND ca.id_c = ac.account_id
 AND ca.id_c =
 AND = ac.contact_id
 AND b.bean_module = 'Contacts'
 AND b.bean_id =
 AND b.email_address_id =
CREATE VIEW `accounts_for_cis2` AS
 `accounts_cstm` ca,
 accounts a,
 users u
 ca.id_c = and = a.assigned_user_id
ldapsearch -x -D "uid=search-user,ou=People,dc=example,dc=com" \
           -W -H ldap:// -b "ou=People,dc=example,dc=com" \
           -s sub 'uid=test-user'

was not aware this, but already on Fedora

sudo postconf -e defer_transports=smtp;sudo postfix reload : pause email delivery but still accept email.
postcat -qv 2E4C42104D
sudo postconf -e defer_transports=;sudo postfix reload;sudo postfix flush : unpause mail delivery… resume email delivery after it has been paused

postsuper -d ALL

postsuper -d [msgid] : delete one email with id [msgid]; previously obtained with a command such as mailq|grep -i [string] or mailq|more

postfix reload : after any changes to the configuration the server has to be reloaded to read the new configuration

postfix -f : flush the mail queue… to help postfix resume delivery faster after it has been paused such as after the computer reconnected