Christian Weisgerber wrote:
> On 2019-08-16, Jan Stary wrote:
>
> >> Does that mean openrsync tries to mmap() the entire file?
> >> The machine only has 256MB of memory, but it does transfer
> >> a test file of 300MB, so that can't be it.
> >
> > I forgot about 1GB swap, so that's why it works
On 2019-08-16, Jan Stary wrote:
>> Does that mean openrsync tries to mmap() the entire file?
>> The machine only has 256MB of memory, but it does transfer
>> a test file of 300MB, so that can't be it.
>
> I forgot about 1GB swap, so that's why it works
> for files up to around 1.2G, but not large
On Aug 16 10:43:41, h...@stare.cz wrote:
> Does that mean openrsync tries to mmap() the entire file?
> The machine only has 256MB of memory, but it does transfer
> a test file of 300MB, so that can't be it.
I forgot about 1GB swap, so that's why it works
for files up to around 1.2G, but not larger
hi everyone
#
# internal interface
INT_IFACE = "em0"
# external wan interface
EXT_IFACE = "bge0"
# wireless interface
WIRE_IFACE = "em1"
# openvpn interface
VPN_IFACE = "tun0"
LO_IFACE = "lo"
LO_ADDR_INET4 = "127.0.0.1"
LO_ADDR_INET6 = "::1"
On Fri, Aug 16, 2019 at 02:12:28PM +0200, Pierre Emeriaud wrote:
> x
>
> Le ven. 16 août 2019 à 12:34, Tor Houghton a écrit :
> >
> > Is there a way to get this information without using 'strings' and 'grep'?
>
> $ doas what /bsd
> /bsd
> OpenBSD 6.5-current (GENERIC.MP) #158: Tue Jul 30 15:
Joe Davis wrote:
> By the looks of it, openrsync does attempt to map the entire file, from
> usr.bin/rsync/uploader.c:
>
> mapsz = st.st_size;
> map = mmap(NULL, mapsz, PROT_READ, MAP_SHARED, *fileinfd, 0);
>
> The likely reason for your out of memory error is the default datasize
> in
By the looks of it, openrsync does attempt to map the entire file, from
usr.bin/rsync/uploader.c:
mapsz = st.st_size;
map = mmap(NULL, mapsz, PROT_READ, MAP_SHARED, *fileinfd, 0);
The likely reason for your out of memory error is the default datasize
in login.conf. IIRC on some arches it'
x
Le ven. 16 août 2019 à 12:34, Tor Houghton a écrit :
>
> Is there a way to get this information without using 'strings' and 'grep'?
$ doas what /bsd
/bsd
OpenBSD 6.5-current (GENERIC.MP) #158: Tue Jul 30 15:25:51 MDT 2019
$ what /home/_sysupgrade/bsd*
/home/_sysupgrade/bsd
OpenBSD 6.6
On Fri, Aug 16, 2019 at 12:10:21PM +0200, Tor Houghton wrote:
> My /bsd contains the following:
>
> OpenBSD 6.5 (GENERIC) #2: Tue Jul 23 23:21:38 CEST 2019
>
> I _think_ this means that the kernel has been built/relinked twice, with the
> date when this was done. (Please do correct me if I am wr
Hi Tor,
Tor Houghton wrote on Fri, Aug 16, 2019 at 12:10:21PM +0200:
> My /bsd contains the following:
>
> OpenBSD 6.5 (GENERIC) #2: Tue Jul 23 23:21:38 CEST 2019
>
> I _think_ this means that the kernel has been built/relinked twice, with
> the date when this was done. (Please do correct me if
Hello,
My /bsd contains the following:
OpenBSD 6.5 (GENERIC) #2: Tue Jul 23 23:21:38 CEST 2019
I _think_ this means that the kernel has been built/relinked twice, with the
date when this was done. (Please do correct me if I am wrong.)
Is there a way to get this information without using 'strin
This is 6.5-current on an old ALIX (dmesg bellow).
I am syncing its backups to a remote machine with openrsync.
It works on all files except one that is big:
196M/backup/gw.stare.cz/dump.home.0
32.0K /backup/gw.stare.cz/dump.home.1
32.0K /backup/gw.stare.cz/dump.home.2
32.0K /backup/gw.
12 matches
Mail list logo
