search for: susv3

...ntact: rsync-qa@samba.org I'm trying to rsync (with -a to preserve permissions) to a mount point on an NFS server, and it fails when copying a file that is read-only. The problem is that do_mkstemp creates the temp file with the desired user permissions (either with open() or with fchmod(). SUSv3 says that the affect of chmod()/fchmod() on existing open file descriptors is implemtation defined; it also says: Any file descriptors currently open by any process on the file could possibly become invalid if the mode of the file is changed to a value which would deny access to that p...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 The same result without CFLAGS: configure:17300: checking for mblen configure:17356: gcc -o conftest -g -O2 -Wall -Wpointer-arith -Wuninitialized -Wsign-compare -Wformat-security -Wsizeof-pointer-memaccess -Wno-pointer-sign -Wno-unused-result -fno-strict-aliasing -D_FORTIFY_SOURCE=2 -ftrapv -fno-builtin-memset -fstack-protector-strong -fPIE

We have a little soekris box running freebsd that uses racoon for key management. It's used for setting up an ipsec tunnel. I noticed that one of these devices lost the tunnel this morning. I looked in the log and saw this Jul 23 01:37:57 m0n0wall /kernel: pid 80 (racoon), uid 0, was killed: out of swap space I reproduced this problem using this code. #include <stdlib.h> int

# HG changeset patch # User Roger Pau Monne <roger.pau@entel.upc.edu> # Date 1323768129 -3600 # Node ID 7697ee23b08b8eaca9aee4f6b79cf550a490bef7 # Parent 8a84f53376862427f254a017cb52c928dbdd3d32 xenpaging: remove XOPEN_SOURCE The XOPEN_SOURCE define was breaking the compilation under NetBSD. I''ve removed it becasue it is not necessary (at least under NetBSD). If it is necessary

...My open(2) manual page says: "When possible, the file is opened in non-blocking mode. Neither the open nor any subsequent operations on the file descriptor which is returned will cause the calling process to wait." See http://www.opengroup.org/onlinepubs/009695399/functions/open.html for SuSv3/POSIX's description of O_NONBLOCK, which explicitly mentions its behaviour on FIFOs, block specials, and character specials. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

SUSv3 is silent on that definition, but seen several userspace software that expects flock to be defined in that file and complain that it is missing in klibc. Current declaration is in unistd.h. Signed-off-by: maximilian attems <max at stro.at> --- usr/include/sys/file.h | 9 +++++++++ usr/in...

...bl)" failed: file "iconvert.c", line 111 In my test case, we have a plain ASCII string with a KOI8-R locale charset and this: Before the first iconv() call: * ibl = 9 * obl = utflen = 1 After the iconv() call: * k = 0, ibl = 8, obl = 0, errno = EINVAL I'm sitting here with the SUSv3 spec for iconv(), trying to make sense of it all. This is one confusing interface, but I don't think the returned values are wrong. Which would render the expectations in the assert() wrong. Opinions? -- Christian "naddy" Weisgerber naddy@mips.inka.de -...

Ian Jackson: > I recently encountered a bug where some ssh login sessions would > apparently inherit a blocked SIGALRM. A web search showed up two > relevant threads: > http://lists.suse.com/archive/suse-linux-e/2005-Dec/2628.html > http://marc.theaimsgroup.com/?l=openssh-unix-dev&m=113533337923128&w=2 > et seq - but sadly no answers. > > Experimentation with

...tecnical note: > >Instead of all those ifndef,define,endif lines with >literals just so you can OR them, cut to the quick with > > #ifndef ALLPERMS > #define ALLPERMS 07777 > #endif > >ALLPERMS is a BSDism that even shows up in the linux headers. > >Since POSIX and SUSv3 specify that the actual mode_t >bits are implementation specific I'm just a trifle leery of >adding this in. We support some rather strange systems >although ACCESSPERMS and INITACCESSPERMS don't appear to >have bitten us so far. My paranoid side says that the >actual value...

These days, sshd.c has: static void grace_alarm_handler(int sig) { ... if (getpgid(0) == getpid()) { signal(SIGTERM, SIG_IGN); killpg(0, SIGTERM); } sigdie(...); } however (really) old BSDs do not have getpgid(). They do have getpgrp(), which does what we want here. The question is what to do if we have neither: return the pid (and thus

Under Aix directories have the mode 024xxxx instead of the customary 04xxxx. Because of this when you sync a directory to or from an Aix system it's never up to date. Here is a patch which fixes this. It causes rsync to look at only the bits that chmod actually influences, 07777, when deciding whether or not the modes differ. I was surprised there wasn't an existing constant for 07777,

Hello, Greetings to all. I am a newbie to rsync. I have a problem,for which I could not find the solution in Rsync Faq o Matiq. Even google couldnt give any solution. So finally I am here.. Currently I am using Rsync to backup data from two different servers. server (a) and sserver (b). The data from servers a & b is rsynce'd to my third machine (c). I have implemented ssh.

I know it is just after a release, but I'm trying to see how the regression tests look on Tru64. I hadn't had a chance to really look at them before because I didn't have sudo installed on Tru64 (now I do). Anyway, for the 3.9p1 release, all of them run except for a couple of problems: - agent-ptrace fails; it looks like setgid isn't enough to kill tracing under Tru64, and I

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 configure:17280: result: no configure:17300: checking for mblen configure:17356: gcc -o conftest -O3 -m64 -mtune=native -pipe -Wall -Wpointer-arith -Wuninitialized -Wsign-compare -Wformat-security -Wsizeof-pointer-memaccess -Wno-pointer-sign -Wno-unused-result -fno-strict-aliasing -D_FORTIFY_SOURCE=2 -ftrapv -fno-builtin-memset

Paolo Bonzini <pbonzini at redhat.com> writes: > Il 28/05/2013 19:32, Michael S. Tsirkin ha scritto: >>>> > > + >>>> > > + switch (addr) { >>>> > > + case offsetof(struct virtio_pci_common_cfg, device_feature_select): >>>> > > + return proxy->device_feature_select; >>> > >>> >

http://bugzilla.mindrot.org/show_bug.cgi?id=1102 Summary: C program 'write' with zero length hangs Product: Portable OpenSSH Version: 4.1p1 Platform: PPC OS/Version: AIX Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo: bitbucket at mindrot.org ReportedBy: timc at

http://bugzilla.mindrot.org/show_bug.cgi?id=581 Summary: SFTP "ls" listings never end Product: Portable OpenSSH Version: -current Platform: Alpha OS/Version: OSF/1 Status: NEW Severity: major Priority: P2 Component: sftp-server AssignedTo: openssh-bugs at mindrot.org ReportedBy:

...l, and IEEE POSIX 1003.2, suggests this should check the mode bits, + * not use access(): + * + * True shall indicate only that the write flag is on. The file is not + * writable on a read-only file system even if this test indicates true. + * + * Unfortunately IEEE POSIX 1003.1-2001, as quoted in SuSv3, says only: + * + * True shall indicate that permission to read from file will be granted, + * as defined in "File Read, Write, and Creation". + * + * and that section says: + * + * When a file is to be read or written, the file shall be opened with an + * access mode corresponding to the...

...S_H +#define OPEN_MAX 20 + #define CHAR_BIT 8 #define SHRT_BIT 16 #define INT_BIT 32 commit 6c82efff8561f0abdaea3054a7170f0aa4605fd6 Author: maximilian attems <max at stro.at> Date: Mon Sep 5 10:56:35 2011 +0200 [klibc] include: [sys/file.h] define flock(2) there SUSv3 is silent on that definition, but seen several userspace software that expects flock to be defined in that file and complain that it is missing in klibc. Current declaration is in unistd.h. Signed-off-by: maximilian attems <max at stro.at> diff --git a/usr/include/sys/fi...

...runs to be on filesystem > boundaries for incrementals to work. And, it probably doesn't handle > the options that amanda needs. Theory, meet practice. You assume "GNU Tar" is the "standard." ;-> It's not, never has been, and is years late to the POSIX-2001/SUSv3 party. As far as not crossing filesystem boundaries, that is easily accomodated. > By 'first', I meant before RH 4.x, which in my opinion really drove > the popularity of Linux simply because it had a decent installer > that came up working on most hardware at the time. Freebsd...