Prototype-X

SET @history_interval = 7;
SET @trends_interval = 90;

DELETE FROM alerts WHERE (UNIX_TIMESTAMP(NOW()) - clock) > (@history_interval * 24 * 60 * 60);
DELETE FROM acknowledges WHERE (UNIX_TIMESTAMP(NOW()) - clock) > (@history_interval * 24 * 60 * 60);
DELETE FROM events WHERE (UNIX_TIMESTAMP(NOW()) - clock) > (@history_interval * 24 * 60 * 60);

DELETE FROM history WHERE (UNIX_TIMESTAMP(NOW()) - clock) > (@history_interval * 24 * 60 * 60);
DELETE FROM history_uint WHERE (UNIX_TIMESTAMP(NOW()) - clock) > (@history_interval * 24 * 60 * 60);
DELETE FROM history_str WHERE (UNIX_TIMESTAMP(NOW()) - clock) > (@history_interval * 24 * 60 * 60);

Prototype-X

Материалы по Go (golang)

На русском языке

Мануалы и туториалы

• [Введение в программирование на Go][1]
• [Маленькая книга о Go][3]
• [Эффективный Go][2]
• Есть еще [Краткий пересказ Effective Go на русском языке][4], но 2009 года

Prototype-X

HP Smart Storage Admin CLI (ssacli) installation and usage on Proxmox PVE (6.x)

Why use HP Smart Storage Admin CLI?

You can use ssacli (smart storage administrator command line interface) tool to manage any of supported HP Smart Array Controllers in your Proxmox host without need to reboot your server to access Smart Storage Administrator in BIOS. That means no host downtime when managing your storage.

CLI is not as convenient as GUI interface provided by BIOS or desktop utilities, but still allows you to fully manage your controller, physical disks and logical drives on the fly with no Proxmox host downtime.

ssacli replaces older hpssacli, but shares the same syntax and adds support for newer servers and controllers.

Installation

Prototype-X

Latency Comparison Numbers (~2012)
----------------------------------
L1 cache reference                           0.5 ns
Branch mispredict                            5   ns
L2 cache reference                           7   ns                      14x L1 cache
Mutex lock/unlock                           25   ns
Main memory reference                      100   ns                      20x L2 cache, 200x L1 cache
Compress 1K bytes with Zippy             3,000   ns        3 us
Send 1K bytes over 1 Gbps network       10,000   ns       10 us
Read 4K randomly from SSD*             150,000   ns      150 us          ~1GB/sec SSD

Prototype-X

#Container Resource Allocation Options in docker-run

now see: https://docs.docker.com/engine/reference/run/#runtime-constraints-on-resources

You have various options for controlling resources (cpu, memory, disk) in docker. These are principally via the docker-run command options.

##Dynamic CPU Allocation -c, --cpu-shares=0
CPU shares (relative weight, specify some numeric value which is used to allocate relative cpu share)

Prototype-X

iLO Remote Console

This small script lets you start iLO Java-based console from shell.

But why not HTML5?

• iLO 2/3 doesn't have HTML5 console
• Mounting local (from the client computer) ISOs is PAINFULLY slow via HTML5 client

TL;DR

If you just start it, it will ask you for everything:

Prototype-X

#!/bin/sh

# set hostname
echo <%= hostname %> > /etc/hostname
/etc/init.d/hostname.sh

# Set up networking
cat > /etc/network/interfaces << EOF
# The loopback network interface
auto lo

Prototype-X

How to keep using adblockers on chrome and chromium

1. google's manifest v3 has no analouge to the webRequestBlocking API, which is neccesary for (effective) adblockers to work
2. starting in chrome version 127, the transition to mv3 will start cutting off the use of mv2 extensions alltogether
3. this will inevitably piss of enterprises when their extensions don't work, so the ExtensionManifestV2Availability key was added and will presumably stay forever after enterprises complain enough

You can use this as a regular user, which will let you keep your mv2 extensions even after they're supposed to stop working

Linux

In a terminal, run:

Prototype-X

sample config

user@mx04> show configuration snmp | no-more
location "lab";
v3 {
    usm {
        local-engine {
            user user1_noauth {
                authentication-none;
            }

Prototype-X

Отличный вопрос. Я проанализировал предоставленные Release Notes для версий с S3 по S10, выделив наиболее важные исправления для вашего стека технологий на QFX5100.

Ключевой вывод: Настоятельно рекомендуется обновление как минимум до 21.4R3-S7, а в идеале — до последней доступной 21.4R3-S10. Версия S2 является довольно старой и содержит множество критических багов, исправленных в последующих сервисных релизах.

Вот разбор по категориям и версиям, с указанием наиболее важных багфиксов.

Критически важные исправления

Эти исправления предотвращают потерю связи, перезагрузки маршрутизаторов (RPD crash) или уязвимости безопасности.