similar to: [PATCH] Add minimal mkstemp(3) implementation.

tags 516774 = patch tags 516294 = upstream thanks Hi! Please find attached a diff closing #516774 by adding mkstemp(3), again with a minimalistic pseudo-arc4random(3) behind it. I?ve revisited the code. An mkstemp testsuite from the ?net shows it works, except for not caring how many ?X?en are in the template. Addressing #516294, it allows compiling and linking an mksh from today?s CVS against

Hi, after a year, I decided to hack on klibc again. I?ve reworked both the patch to add mkstemp(), discussing to use AT_RANDOM as cheap entropy source on IRC (if there will ever be another entropy consumer, I can quickly write a minimal arc4random() seeded from it, as it has only 16 octets), capable of making a working mksh (static and shared) on amd64/xen, and the m68k support code, leading to

Hi sh4 porters, I?ve just fixed a regression of klibc to build from source on sh4 using the sumotsu.debian.net porterbox (thanks for making one available) and found a problem with your archi- tecture: all binaries built with klibc (shared and static) get a SIGILL (illegal instruction). I suspect that different CFLAGS are needed. Please, someone, have a look at it; a release of klibc 2.0 upstream

Pardon me if this is already known -- Theo, at least, had never heard of a Unix doing this. mkstemp() under Linux claims to conform to BSD4.3, but BSDs (FreeBSD and OpenBSD, at least) seem to have a slightly different behavior. Under Linux, new files are created with mode 0666, while under BSDs new files are created with mode 0600. A user need only set his umask to 0 and he will be able to

Hello all I have two Linux boxes. The first one is samba servers for the Windows clients. The second one is backup storage. So every few hours rsnc synchronises the data directories on the second machine. They are Suse Linux 9 Linux max 2.6.11.4-21.7-smp #1 SMP Thu Jun 2 14:23:14 UTC 2005 i686 i686 i386 GNU/Linux rsync version 2.6.3 protocol version 28 From time to time I get errors reported,

Hi, --- + rsync -av --timeout 120 /home/20070129_1012/status.csv --port 5873 fileserver::test/20070129_1012/status.csv building file list ... done status.csv rsync: mkstemp "/20070129_1012/.status.csv.IWS933" (in test) failed: No such file or directory (2) sent 347 bytes received 38 bytes 770.00 bytes/sec total size is 228 speedup is 0.59 rsync error: some files could not be

Hello everyone, Server1: Harmony Server2: Peace I've been using rsync 2.6.4 since some time now, without any problem. I "copy" files from Server2 to Server1 (making Server1 a mirror of Server2). The command line used on Server1 was: rsync -vrlpogt --delete-after Server2::Img/ /LocalImg I was copying files from Server2 (module Img) to Server1 (in /LocalImg). We had a problem

http://bugzilla.mindrot.org/show_bug.cgi?id=44 ------- Additional Comments From jan.iven at cern.ch 2002-07-05 01:11 ------- Update: I have reported this to the glibc people, who say that they will not modify their mkstemp(). (http://bugs.gnu.org/cgi-bin/gnatsweb.pl?debug=&database=default&cmd=view+audit-trail&cmd=view&pr=3573) Attached is a patch to configure{ac,in} to

The setup... Transport is via SSH. BoxA : Ubuntu 8.10 BoxB : Mac OS X 10.4.11 If I use rsync v2 to transfer data from BoxA to BoxB everything works fine. However, if I use rsync v3 to transfer the data, the following error is reported : rsync: mkstemp "/path/to/somefile/file.pm.JKQczN" failed: No such file or directory (2) If at all possible,

We are using rsync to push DNS records from one machine (running rsync 2.5.6 as a client process on Debian woody) to a collocation server ( running rsync 2.5.6 as a daemon on RedHat 7.3). To test this process we are using a script that pushes one file from the Debian box to the collocation server. It appears that a file transfers, but upon checking there is no file transfer and an error in the

We are trying to enable large file support for everything built for ARM on ChromeOS and openssh uses mkstemp which has a 64-bit version for compatibility with open64. When looking into enabling the large file support flags, I noticed: `void start_progress_meter(const char *, off_t, off_t *);` in progressmeter.h which would have different ABIs with and without large file support. You all

On Wed, 22 Mar 2023, Allen Webb wrote: > We are trying to enable large file support for everything built for > ARM on ChromeOS and openssh uses mkstemp which has a 64-bit version > for compatibility with open64. When looking into enabling the large > file support flags, I noticed: > > `void start_progress_meter(const char *, off_t, off_t *);` > > in progressmeter.h

https://bugzilla.samba.org/show_bug.cgi?id=11978 Bug ID: 11978 Summary: mkstemp failed: File name too long (36) when filename is under the limit Product: rsync Version: 3.1.1 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core

http://bugzilla.mindrot.org/show_bug.cgi?id=44 ------- Additional Comments From djm at mindrot.org 2002-05-13 15:39 ------- Have you filed a bug in the glibc bug tracking system? BTW, how did you compile with krb4 on Redhat 7.2 without running over libdes conflicts? ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

Le 22/08/2013 14:36, Thorsten Glaser a ?crit : > leroy christophe dixit: > >> If I set prefix to / and INSTALLROOT to /opt/klibc, klcc is not able to find >> the include files >> If I set prefix to /opt/klibc and SHLIBDIR to /opt/klibc/lib, it is the target >> that tries to load klibc.so from /tmp/klibc-install/lib instead of /lib > INSTALLROOT is some sort of

hi All, Our configuration is, ISDN PRI lines connected to Asterisk Server, SIP users connected to Asterisk We route calls from ISDN PRI to SIP users, We did a CVS upgrade few days ago, now the sip users(CISCO phones) are experiencing, distortion of voice while they are engaged in a call. ie, SIP users can here the call clearly, but the outside caller heres distorted voice. ie, to

Hi all, I'm running rsync version 2.6.3 protocol version 28 on Solaris 8 and am having a problem. We have some scripts that wrap around rsync and generate a list of files to transfer from the sending system (regardless of whether that directory exists on the receiver). I was expecting rsync to fail when transferring files with a path that doesn't exist on the receiver (in fact

I'm not really what you would call a linux newbie, but I managed to run into a problem with rsync that has me stumped. I want to conduct un-attended backups of various files and directories over about 3000 miles of Internet, so I chose sshd and rsync for the job. I wrote a pair of scripts to do the job, the first to run incremental tars on the localhost, the second to run the rsync client.

Hello, I am quite new to asterisk. I managed to connect our 2 branch offices with asterisk. In one side, our linux asterisk box is connected to the leased line going to our other office and on the other side its connected to office PBX through a channel bank. This installation is running smoothly, except for one thing. If an extension is busy, i want to transfer that call to a near by one,

Hi, after changing mksh to no longer use mkstemp, I decided to try and build mksh-static with klcc on most platforms, in Debian. Here are the results by Debian architecture: alpha (4) fails amd64 works armel works armhf (3) fails i386 works ia64 works m68k (1) workaround mips works mipsel works powerpc (2) fails ppc64 works (!) s390 works s390x works sparc works Architectures not listed either