similar to: scp "Bad address" errors with strange filesystem block sizes

I'm fond of the "-a" (archive) option of cp, and I'm a heavy user of scp, so I guess it's inevitable that I would eventually add support for "-a" to scp. :-) Actually, it's a "-L" flag for preserving symlinks, and a "-a" flag that is shorthand for "-Lpr". Please let me know if I'm not doing this right.... I made a great

Hi, I have made a patch which improves scp utility. It adds two new features: rate limit and resume support. With rate limit it's possible to limit transfer speed. Resume allows to continue file transfer where it was last interrupted. Also the progress meter was improved. Here is my patch, please send comments about it and what I can do better if there is something to fix. ---

A while back someone posted a patch for scp that updates it to deal with files > 2gb by using 64 bit offsets as defined by LFS (Large File Sumit). I belive the patch was tested on Linux but maybe not on other systems that support largefiles. I've tried this under Solaris and scp fails with a broken pipe on only the second write to the pipe between scp and ssh if the file is over 2gb. If

The existing APIs guestfs_stat, guestfs_lstat and guestfs_lstatlist return a stat structure that contains atime, mtime and ctime fields that store only the timestamp in seconds. Modern filesystems can store timestamps down to nanosecond granularity, and the ordinary glibc stat(2) wrapper will return these in "hidden" stat fields: struct timespec st_atim; /* Time of last

I'm curious how to go about submitting a suggestion that affects both the original BSD version and the portable release. A few days ago I sent off a BSD-relative patch to openssh at openssh.com. Is this the right thing to do? I didn't hear anything back, but it's only been 3 days, so I'm probably just being too antsy. In the meantime, maybe someone else out there would like to

< This patch is against openssh-2.5.2p2 > Here's a few lines we changed a while back in "scp.c" to get it to transfer large (>2GB) file on a 32-bit system using LFS. Obviously, you don't want the line hard-coded in that sets _FILE_OFFSET_BIT=64, but perhaps you could make it a configure option. (Is it already perhaps?) Do you agree that these lines are neccessary

Greetings, Attached patch "fixes" the following warning while compiling with gcc 3.4.5, openssh 4.3p2 in an AMD64 Linux system, which is triggered by the comparison between off_t (signed long) and size_t (unsigned long) as shown : scp.c: In function `source': scp.c:632: warning: comparison between signed and unsigned scp.c:639: warning: comparison between signed and unsigned I am

rcp -r is broken in 4.7 and 4.8. A fix is included below. The web-based bug interface is currently disabled so I can't open a bug report. I believe the person that provided the patch to me also indicated the problem exists in 5.0, but I'm unable to verify that since I'm only running 4.x. I think they monitor this list so I'll let them speak up if they choose to. >--- rcp.c~

Dear OpenSSH porting developers, finally I succeded in porting OpenSSH to QNX 4. To get things going I had to take over some definitions from Linux' include files, since they are not available under QNX (e.g. the howmany makro, NFDBITS, the lastlog structure). With this email I send a patch with all my changes as well as the file "qnx-term.h" which I created because IXANY and

Dear R community, I'm trying to graphically illustrate my data with a worlmap. Unfortunately, my data is partly on country basis and partly on regional basis (e.g. certain African countries are aggregated to one region). I am using the package rwoldmap. The data on country basis can be mapped, but our defined regions cannot be identified in R. Therefore, all the countries in these

Dear All, We are currently working with very large datasets which even in R require a lot of calculation time. Is there an option of including a function/ tool or something alike which shows the remaining time of calculation? Just to see whether there is any progress or whether anything has crashed and to get a feeling whether we have to wait for 5 min or 30min... Any help is greatly

Dear All, at the moment I am using R for calculations of large databases. Unfortunately, R only manages to complete certain operations at some times, and not at others. I usually get the error message "cannot allocate vector of size XX" I am using the 64-bit version with Windows 7. While my computer has 8 RAM, I do have a feeling that R cannot use all of it. Searching online, I

I think my first send was eaten by elm.. Yuck I hate this programm.. Anyawys, first the disclaimer: This is barely tests, I submit this to the general population, but I will not submit this for review of rest of the OpenSSH team. Mainly because it is horrible at best. dealing with alarm() in a sane way is not fun. It does not compile clean, but works. IF anyone cares to clean it up..

1) A lot (but not all) of my smbd / nmbd logs are going to /var/log/messages instead of /var/log/samba/ I tried a couple of things in syslog.conf, but just don't know the magic word for samba logs. 2) I'm getting lots of "couldn't find service" errors. I had: [data] path = /data read only = no public = yes browseable = yes writeable

Again, this has been lightly tested. I think there still are a few glitchs. 1. stole progressmeter() from scp.c - clean up and simplified a little to remove the 'flag' status. It now understands how to initialize itself and how to terminate itself. Along with a malloced status bar instead of the original fix width bar. 2. removed all initialization code from scp.c for progressmeter()

Hello, I'm working in adding support for 64-bit integers to my target. I'm using LLVM to decompose the 64-bit integer operations by using 32-bit registers wherever possible and emulating support where not. When looking at the bit shift decomposition I saw what seems to be a bug in the implementation. The affected function is ExpandShiftWithUnknownAmountBit in LegalizeIntegerTypes.cpp.

I don't know if anyone would be interested in this but I'm including a patch to allow for offsets when transferring files with SCP. It's pretty simple and assumes the user knows what they are doing (for example, if transferring with a wild card the offset would apply to all files). -A is the number of bytes offset from the beginning of the files. -Z is the number of bytes inset

Hi Javier, > The problem is the implementation of the expansion. Perhaps an example > can help illustrate better. Take the case of a 64-bit integer shifted > left by say 6 bits and is decomposed using 32-bit registers. Because 6 > is less than the 32 (the register size) the resulting low part should be > equal to the source low part shifted left by 6 bits. The current >

Duncan, It seems that the code you pasted came from the function ExpandShiftByConstant and indeed it looks correct. In my example I used 6 as the shift amount but forgot to mention that it's stored in a register. Otherwise ExpandShiftWithUnknownAmountBit wouldn't get called. Below is the execution of DAGTypeLegalizer::ExpandIntRes_Shift() using my example showing how

Hi all, I have problems in a dataframe variables types. Look: from a loop function: for(...){ ... dados.fin <- rbind(dados.fin, c(L=j, A=j^2, Nsp=nsps, N=length(amosfin$SP), AmT="am",NAm=nam, AMST=amst)) dados.fin <- rbind(dados.fin, c(L=j, A=j^2,