Blog

Troubleshooting Common Auto Start-Stop Problems: A Quick Guide

How Auto Start‑Stop works (brief)

Auto Start‑Stop temporarily shuts off the engine when the vehicle is stopped (e.g., at lights) and restarts it when you release the brake or engage the clutch. It uses the battery, starter/motor, engine control unit (ECU), and sensors to decide when to stop and restart.

Quick checklist — start here

1. Battery health: Weak or aged batteries often disable the system. Check battery voltage (should be ~12.6V at rest) and for corrosion on terminals.
2. 12V battery state of charge: If the charge is low, the system will remain off. Ensure proper charging by driving or charging with a suitable charger.
3. Battery temperature: Extreme cold or heat can prevent Start‑Stop from operating. Park in milder conditions if possible.
4. Brake/clutch position sensor: Faulty sensors prevent restart. Check for error codes or inconsistent pedal behavior.
5. Seatbelt/door status: Open doors or unbuckled seatbelts can inhibit the system on some models.
6. Engine temperature: If the engine isn’t in optimal temperature range the system may be disabled; warm vehicle up properly.
7. Accessory load: High electrical loads (AC, heated seats, defogger) can keep the system off. Turn off nonessential accessories.
8. Fault codes/ECU: Use an OBD‑II scanner to read stored codes that may point to sensors, starter, or battery management issues.
9. Starter/alternator condition: Worn starters or charging faults can interfere with restarts — test these components if other checks pass.
10. Software updates: Manufacturers sometimes release ECU updates to improve Start‑Stop logic — check dealer/service advisories.

Quick diagnostic steps (5–10 minutes)

1. Try a cold and warm start cycle: note whether Start‑Stop works only when warm or not at all.
2. Turn off AC/heated features and retry to rule out accessory load.
3. Check dash for Start‑Stop disable indicator or warning lights.
4. Use a multimeter to measure battery resting voltage and charging voltage (~13.7–14.7V with engine running).
5. Scan for OBD‑II codes; note and look up any codes related to battery, starter, crank/cam sensors, or body control modules.

Common symptoms and likely causes

• System disabled message + no start-stop: weak battery, ECU fault, or explicit manual disable.
• Start fails only when cold: engine temperature sensor or strategy prevents operation.
• Intermittent operation: sensor noise (brake/clutch), battery borderline health, or wiring/connectors.
• Frequent warning lights after restarts: ECU or charging system issues; check alternator and grounding.

When to seek professional help

• Persistent fault codes after battery/service reset.
• Starter or alternator tests fail.
• Complex wiring or module replacement needed.
• If battery is serviceable but Start‑Stop remains disabled — dealer may need ECU reprogramming.

Preventive tips

• Keep battery terminals clean and tight.
• Replace battery when near end of life; use manufacturer‑specified type (many systems require AGM/absorbed glass mat batteries).
• Follow service intervals and software recalls/updates.
• Avoid excessive accessory use during short-stop city driving.

Date: February 8, 2026

Streamline Your Workflow with TrayLauncher: Tips & Best Uses

TrayLauncher is a lightweight utility that keeps your most-used apps, scripts, folders, and shortcuts accessible from the system tray. If you regularly juggle many tools or switch between projects, TrayLauncher reduces friction so you can focus on work instead of hunting for files or icons. Below are practical tips and best-use patterns to make TrayLauncher earn its place in your daily workflow.

Why use TrayLauncher

• Instant access: Launch apps and files with one click from the tray instead of searching the Start menu or desktop.
• Declutter: Replace desktop icons and oversized taskbars with a compact, organized launcher.
• Context switching: Group items for projects or roles so switching contexts becomes fast and repeatable.
• Automation friendly: Add scripts and command-line tools to the tray for one-click automation.

Getting started: core setup

1. Install TrayLauncher and pin it to start so it runs at login.
2. Open the TrayLauncher settings and create your first group named “Daily”.
3. Add your top 6–10 items: email client, browser profile, editor, communication app, terminal, and a frequently used folder.
4. Assign custom icons and descriptive labels to speed visual recognition.
5. Set hotkeys for your most-used groups or individual entries for keyboard-first workflows.

Organizing for maximum efficiency

• Groups by activity: Create groups like “Work — Project A”, “Communication”, “Dev Tools”, and “Admin”. Only populate groups with items relevant to that activity.
• Pinned vs transient entries: Pin core apps (editor, browser) and use transient entries for files or scripts you’ll need temporarily.
• Color-code or iconize: Use icons consistently (e.g., blue for browser, green for terminal) so muscle memory does the work.
• Limit group size: Keep groups to ~8–12 items to avoid visual overload and speed selection.

Advanced usage patterns

• Project templates: Create a group template per project containing the editor, repo folder, build script, browser with relevant bookmarks, and notes file. Duplicate and customize per new project.
• Script-run shortcuts: Add batch, PowerShell, or shell scripts to execute common tasks (start dev server, deploy, backup). Set them to run minimized and show notifications on completion.
• Context-aware switches: Use multiple groups for different roles (e.g., “Design” vs “Coding”); toggle between groups when shifting tasks to instantly change your toolset.
• Multi-monitor workflows: Place TrayLauncher on your primary display and create monitor-specific groups (e.g., monitor 1: communication, monitor 2: dev) to quickly move focus.

Productivity tips

• Combine with a window manager: Use TrayLauncher for app launching and a window manager for arranging them automatically once opened.
• Use hotkeys for speed: Map the top 3–4 actions to hotkeys so you can open them without touching the mouse.
• Archive old groups: Keep older projects in an “Archive” group instead of deleting—reduces clutter but keeps recoverability.
• One-click documentation: Add README or notes files for projects to the group so context is always one click away.

Security and maintenance

• Review startup items: Periodically check what runs at login and remove anything unnecessary.
• Use descriptive labels for scripts: Include short labels that indicate risk (e.g., “Deploy — Prod (danger)”).
• Back up config: Export your TrayLauncher configuration so you can restore settings after a reinstall or on another machine.

Example setup (recommended)

• Group: Daily — Browser, Email, Editor, Notes, Terminal, Calendar
• Group: Project Alpha — Alpha repo folder, Alpha-dev server script, Alpha notes, Browser with Alpha bookmarks
• Group: Admin — VPN, Remote Desktop, Password Manager, Billing spreadsheet
• Hotkeys: Ctrl+Alt+1 → Daily, Ctrl+Alt+2 → Project Alpha, Ctrl+Alt+D → Terminal

When not to rely on TrayLauncher

• If you need deep application management (virtual desktops, tiling) exclusively, pair TrayLauncher with a dedicated window/desktop manager rather than replacing it.
• Avoid using TrayLauncher for highly sensitive credentials; prefer your password manager’s secure autofill.

TrayLauncher excels when used as a compact, context-aware app-docking station. With a small upfront organization effort—groups, icons, and a few scripts—you’ll save dozens of clicks per day and make context switches smooth and repeatable. Start with a single “Daily” group, add project templates as you go, and refine hotkeys until launching tools becomes second nature.

How Drunk Am I? for Windows ⁄₈.1 — Install, Use, and Tips

Overview

• Lightweight EBAC (estimated blood alcohol content) calculator app (version 1.1.0.7).
• Developer: BAPPS. Runs on Windows 8.1 and Windows 10 (⁄₆₄-bit). File ~2.1 MB. Interface has four panels: Check‑in Time, Standard Drinks, Custom Drinks, and Tab.

Install (assumed Windows 10)

1. Open Microsoft Store (app must be available in the Store for your Windows version).
2. Search “How Drunk Am I?” (developer: BAPPS) or use a trusted download mirror such as Softpedia if Store unavailable.
3. Click Install / Get and follow prompts. If downloading from a third‑party site, scan the file with your antivirus before running.

Basic use

1. Open app and set Check‑in Time (use current time button or enter manually).
2. In Standard Drinks, tap the drink icon multiple times to add quantities (Beer, Wine, Spirits, Shot, Brandy, Fortified Wine).
3. Use Custom Drinks to add non‑standard beverages (name, quantity, ABV) and “Mix” to combine.
4. Open Tab to review items consumed, then press How Drunk Am I? to calculate EBAC, view estimated time to sober, and read a short description of impairment level.

Tips & cautions

• Tip: Enter body weight and sex (if the app asks) for more accurate EBAC estimates.
• Tip: Use Custom Drinks for cocktails or craft beers with unusual ABV.
• Caution: This is an estimate only — do not rely on it to decide whether to drive. BAC can vary by metabolism, medications, food, and health conditions. When in doubt, don’t drive.
• Security: If installing from outside the Microsoft Store, verify the download source and scan the installer.
• Troubleshooting: If the Store version requires Windows 8.1, try running it in compatibility mode or install on a machine with Windows 8.1 / compatible Store support.

Sources: Softpedia app listing and app screenshots/review.

How POP3 Direct Access Works — Setup, Security, and Best Practices

What it is

POP3 Direct Access means an email client connects directly to a mail server using the POP3 protocol (TCP port 110 for plain, 995 for POP3S/TLS) to authenticate, list, download, and optionally delete messages. It’s optimized for single-device access and offline reading.

Quick setup (prescriptive)

1. Server prerequisites: Ensure a POP3-capable MTA/MDA (e.g., Dovecot, Courier, Exchange POP3 service) is installed, updated, and listening on ports 110 and/or 995.
2. DNS & MX: Confirm MX records point to the mail gateway and that the server has an A/AAAA record and a valid TLS certificate for its hostname.
3. Firewall: Allow inbound TCP 995 (preferred) and/or 110 from clients; restrict administrative ports to trusted hosts.
4. Account enablement: Enable POP for user mailboxes (e.g., Exchange: Set-CasMailbox -Identity-PopEnabled $true).
5. Client configuration: Use username (or full email), password, server hostname, port 995 with SSL/TLS. Configure “leave messages on server” if multi-device access is required.
6. Monitoring & backups: Enable logging (auth and mail retrieval), set up alerting for failed logins and unusual volumes, and maintain server-side mailbox backups.

Security best practices

• Use TLS (POP3S on 995) only. Disable plain-text POP (port 110) or require STARTTLS where supported.
• Strong authentication: Enforce strong passwords and, where possible, MFA for account access (or app-specific passwords if MFA blocks legacy auth).
• Limit access: Rate-limit and block repeated failed logins; use IP allowlists for sensitive accounts.
• Harden server: Keep MTA/MDA software patched, disable unused services, run services with least privilege.
• Audit & logging: Log successes/failures, retention for forensic needs, and integrate with SIEM.
• Protect local devices: Require disk encryption, endpoint anti-malware, and backups—POP stores mail locally by default.
• Message integrity/privacy: Use end-to-end signing/encryption (S/MIME or PGP) for sensitive mail, since POP only protects transport.
• Limit attachments/executables: Scan downloaded mail server-side for malware and strip or quarantine dangerous attachments.

Operational considerations & trade-offs

• Single-device vs multi-device: POP3 is best when users access mail from one device; for multi-device sync, prefer IMAP.
• Server storage vs local storage: POP reduces server storage but increases local backup/resilience needs.
• Performance: POP3 is lightweight and simple; large attachments can cause long downloads—consider server-side size limits or attachment offloading.
• Legacy clients: POP3 supports older clients, but legacy authentication poses security risks—mitigate with app passwords and network controls.

Quick checklist (actions to implement)

• Enable POP3S (port 995) and disable/plain-block port 110.
• Deploy valid TLS certs and enforce TLS-only connections.
• Enforce strong passwords and block brute-force attempts.
• Configure logging + SIEM ingestion and enable alerts for anomalies.
• Require endpoint protection and disk encryption on client devices.
• Decide per-user whether to “leave messages on server” and document backup policies.
• Consider migrating most users to IMAP unless single-device offline access is required.

If you want, I can generate sample server config snippets (Dovecot/Exchange) and client setup steps for specific platforms.

Best Practices for Displaying Feeds with an RSS Viewer Web Part

An RSS Viewer Web Part is a simple but powerful way to surface external or internal content in a portal or intranet. To keep feeds useful, performant, and secure, follow these best practices when configuring and embedding RSS feeds.

1. Choose high-quality, relevant feeds

• Relevance: Only add feeds that directly support your site’s goals (news, product updates, team blogs).
• Authority: Prefer official sources or well-known publishers to reduce the risk of inaccurate or low-value content.
• Frequency: Match feed update frequency to the display context—high-frequency feeds for dashboards, lower-frequency for summary pages.

2. Limit number of items and update frequency

• Item limit: Display a reasonable number of items (5–10) to keep pages scannable and reduce load.
• Fetch interval: Set the refresh interval to balance freshness and performance (e.g., every 15–60 minutes for most use cases). Avoid real-time polling unless necessary.

3. Prioritize performance and caching

• Use caching: Cache feed responses server-side or within the viewer to avoid repeated HTTP requests and speed up page loads.
• Lazy load content: Load full feed content or heavy assets on demand (click or expand) rather than all at once.
• Compress and minify: Ensure the page and web part assets are optimized for size.

4. Sanitize and control content rendering

• Strip unsafe HTML: Remove scripts, iframes, and potentially dangerous attributes from feed content to prevent XSS.
• Limit embedded media: Block or sandbox embedded media (videos, widgets) unless explicitly required and trusted.
• Prefer summaries: Show feed titles and short summaries rather than full HTML bodies to reduce risk and clutter.

5. Provide clear UX and accessibility

• Readable layout: Use clear typography, sufficient spacing, and predictable order (newest first).
• Actions: Provide obvious actions—open original, mark as read, save/bookmark.
• Accessibility: Ensure keyboard navigation, ARIA labels for controls, and semantic markup for screen readers.

6. Offer filtering, sorting, and categorization

• Filters: Allow filtering by tag, author, or keyword to help users find relevant items.
• Sorting: Let users choose newest-first or most-relevant order.
• Category feeds: Where possible, surface category-specific feeds rather than a single mixed stream.

7. Respect privacy and security policies

• HTTPS only: Fetch feeds over HTTPS to protect integrity and prevent mixed-content issues.
• No credentials in feeds: Avoid exposing internal tokens or credentials in feed URLs.
• Third-party restrictions: Verify licensing or terms of use for republishing feed content.

8. Monitor and handle failures gracefully

• Graceful degradation: Show a friendly message when a feed is unavailable, and fall back to cached content when possible.
• Rate limits: Detect HTTP errors and implement backoff to avoid hitting provider rate limits.
• Logging: Track feed errors and latency to troubleshoot and improve reliability.

9. Provide administrative controls

• Manage sources centrally: Allow admins to add, remove, and prioritize feeds.
• Permissions: Restrict who can add external feeds to reduce security risk.
• Audit trail: Keep history of feed additions/changes for compliance.

10. Enable discovery and personalization

• Subscribe/Follow: Let users subscribe to specific feeds or authors from the web part.
• Personalization: Show personalized feed selections or saved filters based on user preferences.
• Recommendations: Surface recommended feeds based on user activity or role.

Conclusion

• Implementing these practices will make your RSS Viewer Web Part more reliable, secure, and useful. Focus on relevance, performance, safe rendering, and a clear user experience to maximize the value of syndicated content in your site.

Electronic Record Management System

An Electronic Record Management System (ERMS) is software designed to capture, store, organize, secure, retrieve, and manage records in digital form throughout their lifecycle. ERMS replaces or complements paper-based filing by applying consistent metadata, access controls, retention rules, and audit trails so organizations can reliably preserve evidence of activities, meet regulatory obligations, and improve operational efficiency.

Why ERMS matters

• Compliance: ERMS enforces retention schedules and disposition rules required by regulations (e.g., industry-specific rules, data protection laws), reducing legal risk.
• Security: Role-based access, encryption, and audit logs protect sensitive records and show who accessed or changed files.
• Efficiency: Centralized search, version control, and workflow automation cut time spent locating and processing records.
• Continuity: Digital records are easier to back up, replicate, and include in disaster-recovery plans than paper files.
• Cost savings: Reduced physical storage, less paper handling, and faster processes lower operational costs.

Core components

• Capture & Ingestion: Scanning, email capture, integration with business systems, and bulk import convert documents and data into managed records.
• Metadata & Indexing: Standardized metadata (title, author, date, retention class, tags) enables precise retrieval and lifecycle actions.
• Storage & Archiving: Efficient storage tiers, compression, and archival policies keep active and dormant records appropriately managed.
• Access Control & Security: Authentication, authorization, encryption (at rest and in transit), and audit logging protect confidentiality and integrity.
• Retention & Disposition Management: Automated retention schedules and legal hold capabilities ensure records are retained or destroyed per policy.
• Search & Retrieval: Full-text search, faceted filters, and saved queries speed information access.
• Versioning & Audit Trails: Track edits, maintain previous versions, and produce tamper-evident logs for accountability.
• Integration & APIs: Connectors to ERP, CRM, HR systems, and e-signature tools enable seamless workflows.

Implementation best practices

1. Define scope and governance: Assign records owners, define retention classes, and establish policy for classification and disposition.
2. Assess and map current records: Inventory existing paper and electronic records, prioritize high-value or high-risk sets for early migration.
3. Choose fit-for-purpose technology: Evaluate vendors for scalability, security certifications (e.g., ISO 27001), deployment model (cloud vs on-prem), and integration capability.
4. Standardize metadata and taxonomy: Use a consistent taxonomy and required metadata fields to ensure discoverability and compliance.
5. Plan phased migration: Start with pilot departments, validate processes, and expand iteratively to reduce disruption.
6. Automate retention and legal holds: Implement automated rules and easy legal-hold mechanisms to avoid accidental disposition.
7. Train users and enforce policy: Provide role-based training, simple interfaces, and policy enforcement to drive adoption.
8. Monitor and audit: Regularly review logs, retention actions, and access patterns to detect anomalies and ensure compliance.

Common use cases

• Regulatory recordkeeping for finance, healthcare, and government
• HR personnel files, onboarding documentation, and performance records
• Contracts lifecycle management (creation, approval, renewal, retention)
• Incident and quality management records in manufacturing
• Research data and intellectual property archives for R&D teams

Risks and mitigation

• Data breach: Mitigate with encryption, strong access controls, and regular security testing.
• Poor classification: Reduce with clear taxonomy, mandatory metadata, and automated classification where possible.
• Vendor lock-in: Use open standards (e.g., PDF/A, XML metadata exports), and ensure export/exit plans.
• Incomplete migration: Pilot critical records first, use validation checks, and keep an audit trail of migrated items.

Measuring success

• Time reduction to locate records (e.g., average search time)
• Percentage of records with complete metadata
• Compliance metrics: number of retention violations or audit findings
• User adoption rates and helpdesk tickets related to record access
• Cost savings from reduced physical storage and processing

Conclusion

An Electronic Record Management System is a foundational tool for modern organizations that need reliable, auditable, and efficient handling of records. With clear governance, appropriate technology choices, and phased implementation, ERMS delivers compliance, security, and operational benefits that scale with the organization.

Automate Your Workflows Using Cmdtime — Examples and Scripts

Date: February 8, 2026

Cmdtime is a lightweight command-line utility designed to simplify time-based automation and workflow measurement. This article shows practical examples and ready-to-use scripts to help you integrate Cmdtime into build scripts, CI/CD pipelines, task scheduling, and developer tooling.

What Cmdtime does (brief)

• Measure: capture execution time for commands or scripts.
• Schedule: run commands at specific times or intervals.
• Log: generate structured timestamps and duration logs for later analysis.
• Trigger: run follow-up commands based on timing outcomes (e.g., long-running jobs).

Installation

Assume a typical install via package manager or download. Example (Linux/macOS with Homebrew-style):

bash
Copy CodeCopied
brew install cmdtime # or
curl -sSL https://example.com/cmdtime/install.sh | bash

Basic usage examples

1. Measure a single command:

bash
Copy CodeCopied
cmdtime run – echo “Hello, world!”
# outputs start time, end time, duration, exit code

2. Time a pipeline:

bash
Copy CodeCopied
cmdtime run – bash -lc ‘grep -R “TODO” src | wc -l’

3. Schedule a command once at a specified time:

bash
Copy CodeCopied
cmdtime schedule –at “2026-02-09 02:30” – bash -lc ‘backup.sh’

4. Run a command every N minutes:

bash
Copy CodeCopied
cmdtime schedule –every 15m – bash -lc ‘sync-data.sh’

Example 1 — CI job timing and conditional step

Use Cmdtime to fail a step if it exceeds a threshold, preventing slow builds from progressing.

script: .gitlab-ci.yml snippet

yaml
Copy CodeCopied
stages:
- test 
test:
  stage: test   script:
    - >
      cmdtime run –format json – bash -lc ‘         timeout 10m npm test       ’ > test-time.json || true
    - >
      DURATION=\((jq .duration_ms test-time.json) </span><span class="token scalar" style="color: rgb(163, 21, 21);">      if [ "\)DURATION” -gt 600000 ]; then         echo “Tests exceeded 10 minutes (\(DURATION ms) — failing pipeline" </span><span class="token scalar" style="color: rgb(163, 21, 21);">        exit 1 </span><span class="token scalar" style="color: rgb(163, 21, 21);">      fi</span><span> </span></code></div></div></pre> <h3>Example 2 — Scheduled nightly backup with logging and rotation</h3> <p>Nightly backup script: backup-nightly.sh</p> <pre><div class="XG2rBS5V967VhGTCEN1k"><div class="nHykNMmtaaTJMjgzStID"><div class="HsT0RHFbNELC00WicOi8"><i><svg width="16" height="16" fill="none" xmlns="http://www.w3.org/2000/svg"><path fill="currentColor" fill-rule="evenodd" clip-rule="evenodd" d="M15.434 7.51c.137.137.212.311.212.49a.694.694 0 0 1-.212.5l-3.54 3.5a.893.893 0 0 1-.277.18 1.024 1.024 0 0 1-.684.038.945.945 0 0 1-.302-.148.787.787 0 0 1-.213-.234.652.652 0 0 1-.045-.58.74.74 0 0 1 .175-.256l3.045-3-3.045-3a.69.69 0 0 1-.22-.55.723.723 0 0 1 .303-.52 1 1 0 0 1 .648-.186.962.962 0 0 1 .614.256l3.541 3.51Zm-12.281 0A.695.695 0 0 0 2.94 8a.694.694 0 0 0 .213.5l3.54 3.5a.893.893 0 0 0 .277.18 1.024 1.024 0 0 0 .684.038.945.945 0 0 0 .302-.148.788.788 0 0 0 .213-.234.651.651 0 0 0 .045-.58.74.74 0 0 0-.175-.256L4.994 8l3.045-3a.69.69 0 0 0 .22-.55.723.723 0 0 0-.303-.52 1 1 0 0 0-.648-.186.962.962 0 0 0-.615.256l-3.54 3.51Z"></path></svg></i><p class="li3asHIMe05JPmtJCytG wZ4JdaHxSAhGy1HoNVja cPy9QU4brI7VQXFNPEvF">bash</p></div><div class="CF2lgtGWtYUYmTULoX44"><button type="button" class="st68fcLUUT0dNcuLLB2_ ffON2NH02oMAcqyoh2UU MQCbz04ET5EljRmK3YpQ CPXAhl7VTkj2dHDyAYAf" data-copycode="true" role="button" aria-label="Copy Code"><svg viewBox="0 0 16 16" fill="none" xmlns="http://www.w3.org/2000/svg"><path fill="currentColor" fill-rule="evenodd" clip-rule="evenodd" d="M9.975 1h.09a3.2 3.2 0 0 1 3.202 3.201v1.924a.754.754 0 0 1-.017.16l1.23 1.353A2 2 0 0 1 15 8.983V14a2 2 0 0 1-2 2H8a2 2 0 0 1-1.733-1H4.183a3.201 3.201 0 0 1-3.2-3.201V4.201a3.2 3.2 0 0 1 3.04-3.197A1.25 1.25 0 0 1 5.25 0h3.5c.604 0 1.109.43 1.225 1ZM4.249 2.5h-.066a1.7 1.7 0 0 0-1.7 1.701v7.598c0 .94.761 1.701 1.7 1.701H6V7a2 2 0 0 1 2-2h3.197c.195 0 .387.028.57.083v-.882A1.7 1.7 0 0 0 10.066 2.5H9.75c-.228.304-.591.5-1 .5h-3.5c-.41 0-.772-.196-1-.5ZM5 1.75v-.5A.25.25 0 0 1 5.25 1h3.5a.25.25 0 0 1 .25.25v.5a.25.25 0 0 1-.25.25h-3.5A.25.25 0 0 1 5 1.75ZM7.5 7a.5.5 0 0 1 .5-.5h3V9a1 1 0 0 0 1 1h1.5v4a.5.5 0 0 1-.5.5H8a.5.5 0 0 1-.5-.5V7Zm6 2v-.017a.5.5 0 0 0-.13-.336L12 7.14V9h1.5Z"></path></svg>Copy Code</button><button type="button" class="st68fcLUUT0dNcuLLB2_ WtfzoAXPoZC2mMqcexgL ffON2NH02oMAcqyoh2UU MQCbz04ET5EljRmK3YpQ GnLX_jUB3Jn3idluie7R"><svg fill="none" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg"><path fill="currentColor" fill-rule="evenodd" d="M20.618 4.214a1 1 0 0 1 .168 1.404l-11 14a1 1 0 0 1-1.554.022l-5-6a1 1 0 0 1 1.536-1.28l4.21 5.05L19.213 4.382a1 1 0 0 1 1.404-.168Z" clip-rule="evenodd"></path></svg>Copied</button></div></div><div class="mtDfw7oSa1WexjXyzs9y" style="color: var(--sds-color-text-01); font-family: var(--sds-font-family-monospace); direction: ltr; text-align: left; white-space: pre; word-spacing: normal; word-break: normal; font-size: var(--sds-font-size-label); line-height: 1.2em; tab-size: 4; hyphens: none; padding: var(--sds-space-x02, 8px) var(--sds-space-x04, 16px) var(--sds-space-x04, 16px); margin: 0px; overflow: auto; border: none; background: transparent;"><code class="language-bash" style="color: rgb(57, 58, 52); font-family: Consolas, "Bitstream Vera Sans Mono", "Courier New", Courier, monospace; direction: ltr; text-align: left; white-space: pre; word-spacing: normal; word-break: normal; font-size: 0.9em; line-height: 1.2em; tab-size: 4; hyphens: none;"><span class="token shebang" style="color: rgb(238, 153, 0); font-weight: bold;">#!/usr/bin/env bash</span><span> </span><span></span><span class="token builtin" style="color: rgb(43, 145, 175);">set</span><span> -euo pipefail </span> <span></span><span class="token assign-left" style="color: rgb(54, 172, 170);">LOG_DIR</span><span class="token" style="color: rgb(57, 58, 52);">=</span><span class="token" style="color: rgb(163, 21, 21);">"/var/log/cmdtime-backups"</span><span> </span><span></span><span class="token" style="color: rgb(57, 58, 52);">mkdir</span><span> -p </span><span class="token" style="color: rgb(163, 21, 21);">"</span><span class="token" style="color: rgb(54, 172, 170);">\)LOG_DIR”
TIMESTAMP=\((</span><span class="token" style="color: rgb(57, 58, 52);">date</span><span class="token" style="color: rgb(54, 172, 170);"> -u +</span><span class="token" style="color: rgb(163, 21, 21);">"%Y%m%dT%H%M%SZ"</span><span class="token" style="color: rgb(54, 172, 170);">)</span><span> </span><span></span><span class="token assign-left" style="color: rgb(54, 172, 170);">LOGFILE</span><span class="token" style="color: rgb(57, 58, 52);">=</span><span class="token" style="color: rgb(163, 21, 21);">"</span><span class="token" style="color: rgb(54, 172, 170);">\)LOG_DIR/backup-\(TIMESTAMP</span><span class="token" style="color: rgb(163, 21, 21);">.json"</span><span> </span> <span>cmdtime run --format json -- </span><span class="token" style="color: rgb(57, 58, 52);">bash</span><span> -lc </span><span class="token" style="color: rgb(163, 21, 21);">' </span><span class="token" style="color: rgb(163, 21, 21);">  tar -czf /backups/site-\)TIMESTAMP.tar.gz /var/www/html ‘ > “\(LOGFILE</span><span class="token" style="color: rgb(163, 21, 21);">"</span><span> </span> <span></span><span class="token" style="color: rgb(0, 128, 0); font-style: italic;"># Keep last 30 logs</span><span> </span><span></span><span class="token" style="color: rgb(57, 58, 52);">ls</span><span> -1t </span><span class="token" style="color: rgb(163, 21, 21);">"</span><span class="token" style="color: rgb(54, 172, 170);">\)LOGDIR”/backup-*.json | tail -n +31 | xargs -r rm – 

bash
 ffON2NH02oMAcqyoh2UU MQCbz04ET5EljRmK3YpQ CPXAhl7VTkj2dHDyAYAf” data-copycode=“true” role=“button” aria-label=“Copy Code”>Copy CodeCopied
cmdtime schedule –every 24h –at “02:00” – /usr/local/bin/backup-nightly.sh 

bash
Copy CodeCopied
#!/usr/bin/env bash
echo “migration,started_at,ended_at,durationms” > migrations.csv for f in migrations/*.sql; do
  NAME=\((</span><span class="token" style="color: rgb(57, 58, 52);">basename</span><span class="token" style="color: rgb(54, 172, 170);"> </span><span class="token" style="color: rgb(163, 21, 21);">"</span><span class="token" style="color: rgb(163, 21, 21);">\)f“)
  cmdtime run –format csv –label ”\(NAME</span><span class="token" style="color: rgb(163, 21, 21);">"</span><span> -- </span><span class="token" style="color: rgb(57, 58, 52);">bash</span><span> -lc </span><span class="token" style="color: rgb(163, 21, 21);">"psql -f </span><span class="token" style="color: rgb(54, 172, 170);">\)f“ >> migrations.csv done

bash
 ffON2NH02oMAcqyoh2UU MQCbz04ET5EljRmK3YpQ CPXAhl7VTkj2dHDyAYAf” data-copycode=“true” role=“button” aria-label=“Copy Code”>Copy CodeCopied
cmdtime run –format json – bash -lc ‘long-job.sh’ > job.json DURATION=\((</span><span class="token" style="color: rgb(54, 172, 170);">jq .duration_ms job.json</span><span class="token" style="color: rgb(54, 172, 170);">)</span><span> </span><span></span><span class="token" style="color: rgb(0, 0, 255);">if</span><span> </span><span class="token" style="color: rgb(57, 58, 52);">[</span><span> </span><span class="token" style="color: rgb(163, 21, 21);">"</span><span class="token" style="color: rgb(54, 172, 170);">\)DURATION“ -lt 300000 ]; then
  cmdtime run – bash -lc ‘cleanup-temp.sh’
else
  echo “Job too slow; skip cleanup”
fi