search for: sether

...ode itself, I've tested it with postgresql and mysql. It should be compatible with Oracle, Sybase, and DB2 though these databases are completely untested (i.e. I don't have any of these databases). I still need to write some documentation of new run-time config options. Thanks. -Steve Sether

I'm using rsync to backup multiple directories, i.e. rsync -azq --delete --relative /dog /cat /fish user@rsync-server::modulename Everything works fine, except if I remove a directory from the list of those being backed up, it isn't deleted on the other side. For example: rsync -azq --delete --relative /dog /cat /fish user@rsync-server::modulename /dog /cat /fish are all backed up to

On 12/26/19 6:35 AM, Stuart Henderson wrote: > On 2019/12/25 21:02, Steve Sether wrote: >> Basically I've had to turn on telnet access again, lowering security. > Does it really lower security? The very old embedded OS is not going to > be secure anyway, this type of device should only be used on a trusted > private network. (New embedded OS are often not muc...

Recently I tried to turn on SSH on my 12 year old APC-UPS.? I soon discovered that I couldn't connect to it because my newer version of openssh doesn't support RSA key sizes below 1024 bits. I'd rather not dredge up a big fight, but I _would_ like to express a desire for some form of overriding the minimum key size.? Basically I've had to turn on telnet access again, lowering

I'm not sure keepalive is working the way I think it's supposed to. Here's my test. I've got a large file (approx 1 gig) on the rsync server, and I append a character on the end to make it slightly different. I fire up rsync on the client side and everything works fine until I hit the timeout value. I have this problems when I have a timeout of below 90 seconds. I've tried

I've gotten around to testing the generator hang bug using stunnel under 2.6.7, and I still occasionally get the same problem. It seems to be around 50% of the time. Here's some strace output from the generator and receiver from two runs, one where the generator exits properly, and one where it doesn't. Run 2 hangs indefinately. Run 1 Generator: Process 14581 attached - interrupt

...op you from doing clever things. - Doug Gwyn, in Introducing Regular Expressions (2012) by Michael Fitzgerald Get Outlook for iOS<https://aka.ms/o0ukef> ________________________________ From: openssh-unix-dev <openssh-unix-dev-bounces+j.mccanta=f5.com at mindrot.org> on behalf of Steve Sether <steve at sether.org> Sent: Friday, December 27, 2019 9:50:28 PM Cc: openssh-unix-dev at mindrot.org <openssh-unix-dev at mindrot.org> Subject: Re: Settable minimum RSA key sizes on the client end for legacy devices. EXTERNAL MAIL: openssh-unix-dev-bounces+j.mccanta=f5.com at mindrot.o...

I'm working with my ODBC database logging patch again, and I need some information on how rsync process management works. Essentially I need to close the database connection on a daemon process right before the last process (be it receiver or generator) exits. My question is, which process kills which process? Does the receiver kill the generator, or vice versa? Do they each die

I'd like to patch the generator hang bug recently fixed in my production environment, but it'd be nice to know if a 2.6.7 release is just around the corner. Do you have any kind of estimate on a release date Wayne? I don't care about specifics, but a general idea (a couple weeks, or a couple months) would help a lot in my decision making process.

> I fully agree with Steve here, and dislike developers' attitude of "We > know what's good for you, and since you don't/can't have a clue - we > won't trust you with decisions". Well, I'm on the developers' side. They need to produce a product that _now_ gets installed in some embedded device and is expected to be still secure in 15 years and longer

We've been using Asterisk 16 for a while now, and tried turning on send_rpid = yes in my pjsip config for end points.  This solves a problem we're having where attended transfers aren't updating the CallerID when the transfer is complete (it would show the callerID of the party attempting the transfer, and never update after the transfer happened). The side effect of this change

I've noticed this problem for a while and thought it was my own changes to rsync causing them. I've recently done some tests with vanilla versions of rsync though, and found the same problem. Here's the details. The generator process on an rsync server seems to get stuck in an infinite loop after a client process dies. (The receiver process dies just fine). I can produce this

...---- yhhuang =BB=C6=D3=C2=BB=D4 Server Dept. TeleNav Shanghai Inc. Tel:(21)6337 2220 ext 8651 www.telenav.com -----=D3=CA=BC=FE=D4=AD=BC=FE----- =B7=A2=BC=FE=C8=CB: rsync-bounces+yhhuang=3Dtelenav.cn@lists.samba.org = [mailto:rsync-bounces+yhhuang=3Dtelenav.cn@lists.samba.org] =B4=FA=B1=ED = Steve Sether =B7=A2=CB=CD=CA=B1=BC=E4: 2006=C4=EA3=D4=C216=C8=D5 1:41 =CA=D5=BC=FE=C8=CB: rsync@lists.samba.org =D6=F7=CC=E2: Still getting a generator hang on 2.6.7 I've gotten around to testing the generator hang bug using stunnel under = 2.6.7, and I still occasionally get the same problem. It seems to...

I''m working on the problem I''m having with the generator hanging on the server when the client side dies. This only happens when I''m connecting through stunnel. This is the strace output I''m getting, but I''m not sure how to interpret the output. Can anyone help? write(4, "2005/10/03 13:58:12 [16992] recv"..., 137) = 137 select(8, [7], [3],