From: "Paul Smedley" Received: from vps.smedley.id.au ([23.238.44.164] verified) by 2rosenthals.com (CommuniGate Pro SMTP 5.4.10) with ESMTP id 3300153 for ecs-isp@2rosenthals.com; Thu, 06 Aug 2026 05:31:24 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=smedley.id.au; s=default; t=1786008247; bh=iYcvioZIDUjnDN01p9Tq/9Q1aG8Fu4owBxvZkfgeh8Q=; h=Date:Subject:To:References:From:In-Reply-To:From; b=mCtSgT/prz33FKZhSpPmzYkaWATUFD0ohrfq78k0hFTu2/t11KX5HwifjzbSK5QYv q5RLO5nnhncMqGQF+RAmJWiA1qKlrEIh9pssPwYhyp2AG/Xx0QiFTvC2AdUSGmYu2i IeQ694PjFCGMRKustx7k2WxnFwTOr2uG6tm7ezng= Received: from [192.168.245.251] (smedley.org [45.249.117.21]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange x25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by vps.smedley.id.au (Postfix) with ESMTPSA id B5F7C20155 for ; Thu, 06 Aug 2026 18:54:06 +0930 (ACST) Message-ID: <1f483f71-55b8-434c-86b7-4dc787df53ec@smedley.id.au> Date: Thu, 6 Aug 2026 18:54:04 +0930 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [eCS-ISP] uacme 1.2.4 issue - update To: eCS ISP Mailing List References: Content-Language: en-AU In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Hey Max, On 6/8/26 17:03, Massimo S. wrote: > Il 05/08/2026 23:03, Paul Smedley ha scritto: >> I don't have easy access to an OS/2 box where I am right now, but >> what does chkdll32.exe uacme.exe on the 1.0.19 & 1.2.4 executables say? >> >> My guess is that 1.0.19 had libcurl statically linked and 1.2.4 has >> it dynamically linked. >> >> dynamically linked is preferred as you get security updates for free > > But in this way don't work on servers. Of course it does. > Anyway, if the need is libcurl: > > "YUM install libcurl > Il pacchetto libcurl-7.75.0-3.oc00.pentium4 Þ giÓ installato e > aggiornato all'ultima versione > Niente da fare" > > It means that libcurl is alredy installed, updated and there is > nothing to do. > So what should i install more? > > I guess that developers do not test UACME scheduled, they simply start > it from the > command line, it works, oh well, it's all ok. > > But UACME is a server tool that must run scheduled, or it's unuseful. > I guess that CRON is starting a command prompt window with "less > environment stuff" > and the issue pop out. It's pretty simple, there is some kind of defect in your cron. Steven doesn't appear to have this issue, and I assume he's running 1.2.4 and also scheduling it. > Maybe UACME on /2 has to be compiled with libcurl to work properly. > It *is* compiled with libcurl, otherwise it wouldn't function. Cheers, Paul