The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

    Mastodon

  • Twitter Updates

  • My Flickr Stream

    20140508-Delphi-2007--Project-Options--Cannot-Edit-Application-Title-HelpFile-Icon-Theming20140430-Fiddler-Filter-Actions-Button-Run-Filterset-now20140424-VMware-Fusion-6.0.3.-no-reclaimable
    More Photos

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 4,262 other subscribers

Archive for January 20th, 2020

How to change the control of a Somfy RTS roller blind from 2 to 1 remote – Projectionscreen.net

Posted by jpluimers on 2020/01/20

This procedure works for Somfy RTS motors to:

  • removing an additional channel
  • removing an additional remote

The trick is to have one remote/channel that you want to keep working as you need that one to initiate the deletion process:

  1. On the channel/remote you want to delete
    • Test with the up/down button that it is indeed the one you want to delete
  2. On the channel/remote you want to keep
    1. Test with up/down button
      • The Somfy RTS motor show now work
    2. Press the  small button with a pen
      • The Somfy RTS motor now should “wiggle”
  3. On the channel/remote you want to delete
    1. Press the  small button with a pen
      • The Somfy RTS motor now should “wiggle” again
    2. Test with up/down button
      • The somfy RTS motor should now do nothing
  4. On the channel/remote you want to keep
    1. Test with up/down button
      • The Somfy RTS motor show still work

Via: [WayBack] How to change the control of a Somfy RTS roller blind from 2 to 1 remote – Projectionscreen.net

Videos below the fold:

–jeroen

Read the rest of this entry »

Posted in Hardware, LifeHacker, Power User | Leave a Comment »

OpenSuSE: location of cron jobs

Posted by jpluimers on 2020/01/20

When you look at how to find listed cron jobs, usually the answer is cron -l or cron -u username -l.

However, on OpenSuSE systems, cron jobs can be in different places, and the sysconfig settings have influence on them too.

These files and directories all influence cron:

Directories:

/etc/cron.d/
/etc/cron.daily/
/etc/cron.hourly/
/etc/cron.monthly/
/etc/cron.weekly/

Files:

/etc/sysconfig/cron
/etc/init.d/rc2.d/K01cron
/etc/init.d/rc2.d/S14cron
/etc/init.d/rc3.d/K01cron
/etc/init.d/rc3.d/S14cron
/etc/init.d/rc5.d/K01cron
/etc/init.d/rc5.d/S14cron
/etc/init.d/cron
/etc/news/crontab.sample
/etc/pam.d/crond
/etc/systemd/system/multi-user.target.wants/cron.service
/etc/omc/srvinfo.d/cron.xml
/etc/cron.deny
/etc/crontab

Most are available for other Linux distributions as well, but each one might have slightly different configurations (especially for the directories). Some background reading:

Some details:

  • The crontab -l will only list what is in /etc/crontab.
  • These directories are influenced by/etc/sysconfig/cron, especially the DAILY_TIME variable (see below) for the daily jobs.
    All of the directories are checked every 15 minutes through /usr/lib/cron/run-crons:/etc/cron.daily/
    /etc/cron.hourly/
    /etc/cron.monthly/
    /etc/cron.weekly/
  • That script then uses these files for checking when to run:/var/spool/cron/lastrun/cron.weekly
    /var/spool/cron/lastrun/cron.daily
    /var/spool/cron/lastrun/cron.hourly

The DAILY_TIME variable:

## Type: string
## Default: ""
#
# At which time cron.daily should start. Default is 15 minutes after booting
# the system. Example setting would be "14:00".
# Due to the fact that cron script runs only every 15 minutes,
# it will only run on xx:00, xx:15, xx:30, xx:45, not at the accurate time
# you set.
DAILY_TIME=""

–jeroen

 

Posted in *nix, *nix-tools, cron, Linux, openSuSE, Power User, SuSE Linux, Tumbleweed | Leave a Comment »

SpaceX: Task failed successfully

Posted by jpluimers on 2020/01/20

(thanks John!)

Posted in Uncategorized | Leave a Comment »

Delphi: A few notes on tracking down a use-after free related issue involving interfaces crashing inside System._IntfClear.

Posted by jpluimers on 2020/01/20

A few notes on tracking down a use-after free related issue involving interfaces.

The crash message is like this:

Project UseAfterFreeWithInterface.exe raised exception class $C0000005 with message 'access violation at 0x004106c0: read of address 0x80808088'.

Two things here:

An important note first

Basically any memory value in an exception starting with $8080 and sometimes even $80 should raise suspicion: it usually means a use-after-free case.

You see these errors with FastMM and not with the memory manager as [WayBack] delphi • View topic • Problem with FastMM and D7 explains:

Read the rest of this entry »

Posted in Conference Topics, Conferences, Delphi, Development, Event, Software Development | 8 Comments »

Always use SCSI for your VM guest disks – Jeroen Wiert Pluimers – Google+

Posted by jpluimers on 2020/01/20

Rephrased from [WayBack] Jeroen Wiert Pluimers – Google+:

If you install a virtual machine, ensure the disk controller and disks are SCSI based.

This has many advantages, including:

  • speed (usually the SCSI drivers can be paravirtualised)
  • hot addition of new disks

It holds for virtually any virtualization platform including all non-ancient (less than ~10 year old) versions of:

  • VMware (Workstation, Viewer, but I expect this also to work on vSphere, ESXI, Fusion)
  • Hyper-V
  • KVM (and therefore Proxmox)
  • VirtualBox

Based on my notes in the above link and the links below:

Note this isn’t just for Linux guests/hosts: Most guests (including Windows) can do a SCSI bus re-scan and detect new SCSI devices.

The trick here is that the guest must already have a virtual SCSI controller (adding that will require a reboot of the guest).

Then adding a new SCSI disk on that controller from any host (Windows, Mac, ESXi, vSphere) should work fine.

–jeroen

Posted in ESXi4, ESXi5, ESXi5.1, ESXi5.5, ESXi6, ESXi6.5, Fusion, Hyper-V, KVM Kernel-based Virtual Machine, Power User, Proxmox, View, VirtualBox, Virtualization, VMware, VMware ESXi, VMware Workstation | Leave a Comment »