Displaying 20 results from an estimated 1100 matches similar to: "[Bug 14328] New: usleep() is obsolete, use nanosleep()"
2009 Jun 10
0
[PATCH] Use nanosleep instead of usleep when waiting the hardware.
usleep() was being used without checking its return value. When the
server receives SIGALRM or SIGIO the waits are shortened and random
modesetting failures happen: Use nanosleep and loop around it until
the requested time has elapsed.
---
src/nouveau_hw.c | 2 +-
src/nouveau_local.h | 6 ++++++
src/nv_bios.c | 2 +-
src/nv_crtc.c | 2 +-
src/nv_include.h | 1 +
2011 Oct 03
2
patch: Replace many usleep and some sleep calls with nanosleep
Description: Replace many usleep and some sleep calls with nanosleep.
usleep is stated in its manual page as removed by POSIX.
Contrary to its predecessors, nanosleep semantics is well
defined. The replacement, which is mostly in drivers, is
untested. Supplements http://bugs.debian.org/633791.
Last-Update: Sat, 13 Aug 2011 14:04:48 +0300
Index:
2009 Jul 27
1
supporting --fake-super on opensolaris (zfs) destination
Hello everybody. I wrote a small patch in order to support what I think
is an absolutely needed feature in order to make rsync-based backups
retaining complete ownership permission when writing to an opensolaris
machine using --fake-super.
My goal is making backups of linux boxes to opensolaris/zfs.
In order to make it work just do
patch -p1 < patch_file.txt
inside rsync source tree.
and
2004 Aug 06
2
[PATCH] Solais has nanosleep, too.
This is a patch to configure.in which makes autoconf aware of the
availability of nanosleep() on Solaris.
In Solaris it's in librt, or in libposix4 if you're running an ancient
version (<2.6 I think)
/dale
-------------- next part --------------
Index: configure.in
===================================================================
RCS file: /usr/local/cvsroot/icecast/configure.in,v
2003 Feb 01
1
Build errors on AIX 4.2.1: nanosleep
Hi All.
There are still build errors for scp on AIX 4.2.1 due to lack of
nanosleep (which you can see them live and in colour at [1]). The
attached patch fixes this by using the equivalent nsleep function on AIX
if it exists and nanosleep doesn't.
The patch is mostly the same as the AIX portion of the previous patch
for the nanosleep issue, the major difference being that the #define is
in
2003 Jan 25
1
Build failures: nanosleep on Solaris and AIX 4.2.x
Hi All.
The recent changes to scp caused build failures on Solaris and AIX 4.2
which showed up on the tinderbox[1]. I mentioned the first to djm in
email yesterday but I'm posting after finding the second, in case anyone
else has seen similar problems.
Solaris' nanosleep is in librt (or libposix4 in older versions) which
is not linked. Adding them to configure works fine, however ldd
2005 Apr 12
0
xen-2.0.4+ nanosleep and maybe other errors
Hello!
I''am experiencing some problems and noticed i''m not the first one.
There seems to be no clue about the problem anywhere on the net
so i''m reporintg it here.
(Should this have been directed to the users list instead?)
The main symptom is tail -f <file> failing in nanosleep in domain 0 every
now and then. Sometimes is just gets stuck. Some other long-running
2003 Feb 26
1
nanosleep
Could someone familear with the OpenBSD tree please point me to nanoslep.
scp.c now uses it and it's not in all plattorms so we'll ethier have to add
one to openbsd-compat or ifdef that chunk.
Thanks.
--
Tim Rice Multitalents (707) 887-1469
tim at multitalents.net
2003 Mar 17
3
nanosleep() replacement
I put together a nanosleep() for systems without it.
Please review/test before I commit.
It sems to make UnixWare and Open Server 5 happy.
My SCO Open Server 3 box broke so I can't test it there.
-------------< cut here >----------------
--- openssh/configure.ac.old 2003-03-09 17:16:43.000000000 -0800
+++ openssh/configure.ac 2003-03-16 15:38:28.520560008 -0800
@@ -1483,6 +1483,8 @@
2019 Aug 28
0
Re: [PATCH nbdkit] freebsd: In nbdkit_nanosleep, fallback to calling nanosleep(2).
On 8/28/19 11:14 AM, Richard W.M. Jones wrote:
> Rather than failing to compile on platforms which lack POLLRDHUP such
> as FreeBSD, simply fallback to the old method of sleeping.
>
> This leaves the porting suggestions as a comment in case someone wants
> to implement a better solution for particular platforms.
> ---
> server/public.c | 38
2019 Aug 28
2
[PATCH nbdkit] freebsd: In nbdkit_nanosleep, fallback to calling nanosleep(2).
Rather than failing to compile on platforms which lack POLLRDHUP such
as FreeBSD, simply fallback to the old method of sleeping.
This leaves the porting suggestions as a comment in case someone wants
to implement a better solution for particular platforms.
---
server/public.c | 38 ++++++++++++++++++++++++--------------
1 file changed, 24 insertions(+), 14 deletions(-)
diff --git
2018 May 11
4
[Bug 13433] New: out_of_memory in receive_sums on large files
https://bugzilla.samba.org/show_bug.cgi?id=13433
Bug ID: 13433
Summary: out_of_memory in receive_sums on large files
Product: rsync
Version: 3.1.3
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P5
Component: core
Assignee: wayned at samba.org
Reporter:
2016 Nov 16
0
dovecot pre-install issue
> On 16 Nov 2016, at 13:32, soumitri at iitk.ac.in wrote:
>
> Hi,
>
> Thanks for the reply. I guess RHEL choose v2.2.10 <http://dovecot.org/list/dovecot-news/2013-December/000268.html> as it is a good release with all the things working.
>
> My source of confusion are from
> 1) http://dovecot.org/oldnews.html <http://dovecot.org/oldnews.html>
> I have
2020 Apr 04
0
[PATCH] nonblocking: remove usleep usage
usleep is deprecated under POSIX 2008 and is optionally unavailable
with uClibc-ng.
Signed-off-by: Rosen Penev <rosenp at gmail.com>
---
examples/nonblocking.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/examples/nonblocking.c b/examples/nonblocking.c
index 8e38a94..2f15b80 100644
--- a/examples/nonblocking.c
+++ b/examples/nonblocking.c
@@ -70,8 +70,10 @@ int
2015 Mar 27
0
rsync 3.0.9 segmentation fault
I am now running with --delete --numeric-ids --relative but the problem
still persists.
--
Best regards / Met vriendelijke groet,
Aron Rotteveel
2015-03-27 14:22 GMT+01:00 Kevin Korb <kmk at sanitarium.net>:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Try also removing --delete-excluded. Without those two options there
> should be no reason for rsync to require
2005 Aug 05
1
Problem preserving user/group names on AIX, rsync 2.6.2
I am having a bit of a problem with rsync 2.6.2 on AIX and I was
wondering if this might just be the expected behavior.
When using the -o and -g flags, the user and group names are NOT
preserved on the receiving side, however, the UIDs/GIDs are preserved.
I checked the OLDNEWS file and bugzilla, but could not find any
reference to a problem like this.
Vitals:
-rsync 2.6.2 with security patch
2015 Mar 27
1
rsync 3.0.9 segmentation fault
Hi Roland,
Thanks for the reply. Memory usage on both machines seem fine. The server
has 4GB's of RAM, of which about 3GB is used during the file list build and
about 1.5GB is used during the actual transfer. The client has 16GB of RAM
with a peak usage of 8.5GB.
I just tried three transfers in a row and it consistently breaks at a
certain point, after which I get the "ERROR: out of
2015 Mar 27
0
rsync 3.0.9 segmentation fault
Hi Kevin,
Just did: same result.
--
Best regards / Met vriendelijke groet,
Aron Rotteveel
2015-03-27 14:32 GMT+01:00 Kevin Korb <kmk at sanitarium.net>:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Try it without any --delete options.
>
> On 03/27/2015 09:31 AM, Aron Rotteveel wrote:
> > I am now running with --delete --numeric-ids --relative but the
2015 Mar 27
0
rsync 3.0.9 segmentation fault
Yes, I removed "--no-inc-recursive", without success.
--
Best regards / Met vriendelijke groet,
Aron Rotteveel
2015-03-27 12:24 GMT+01:00 Kevin Korb <kmk at sanitarium.net>:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Have you tried removing --no-inc-recursive yet?
>
> On 03/27/2015 07:19 AM, Aron Rotteveel wrote:
> > Hi Roland,
> >
>
2015 Mar 27
2
rsync 3.0.9 segmentation fault
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Try also removing --delete-excluded. Without those two options there
should be no reason for rsync to require gigs of RAM. Well, unless
the other system has rsync 2.x.
On 03/27/2015 07:29 AM, Aron Rotteveel wrote:
> Yes, I removed "--no-inc-recursive", without success.
>
> -- Best regards / Met vriendelijke groet,
>
>