Bug#820916: Bug 820916 - might be fixed
I spent some time tracing and reproducing what might have been this same bug
820916, and documented my travels on some long forgotten thread over at
Serverfault (as user "ThePythonicCow"):
https://serverfault.com/questions/743412/rsync-hangs-expand-file-list-pointer-array-to-n-bytes-did-move
I ended up building a nice little test case - a shell script of a dozen or so
lines, that reproduced the hang on the rsync version 3.2.3 in my Ubuntu 22.04
system. I posted that test case at the above serverfault page.
Then I was looking around for where to file this as a bug, came across
https://rsync.samba.org, where newer rsync versions, up to 3.2.7 were available.
My hanging test case, which depended on using rsync --verbose option twice, no
longer hangs with 3.2.7
Given that there might not be enough detail in this old 820916 bug to know
whether or not whatever failed back then has been fixed or not, perhaps it's
time to close 820916 as "maybe fixed - reopen if you can still reproduce it."
--
Paul Jackson
p...@usa.net
Bug#461798: [Bug-ed] Bug#461798: warn earlier about readonly files
jidanni wrote: vi warns, emacs warns. Good for them. it usually is a big shock to me After you too have used ed for 20 years, it will no longer shock you. sometimes one discovers there is no place permanent to write at all You don't need a permanent place; /tmp does fine for the minute or two you need it. -- I won't rest till it's the best ... Programmer, Linux Scalability Paul Jackson [EMAIL PROTECTED] 1.940.382.4214 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#461798: [Bug-ed] Bug#461798: warn earlier about readonly files
Did I mention that ed should warn earlier that a file is readonly? I would not agree that's a problem, and I would disagree that such a change should be made. 1) Sometimes I edit a read only file, as a convenient way to do other sorts of operations on it. Opening to read a read-only file is not an error 2) If and when I do try to write out changes to a read-only file, it's easy to deal with the write error by writing my changes out to a tmp file, quitting ed, and applying the changes some other way. 3) ed is legacy software - most users and usages have been around a long time. One should not tweak discretionary details of ed; fix real bugs, but leave the details that are cosmetic or a matter of opinion or fashion -alone-. Each non-essential change to ed breaks something or some usage. -- I won't rest till it's the best ... Programmer, Linux Scalability Paul Jackson [EMAIL PROTECTED] 1.940.382.4214 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#184167: hi Sat, 04 Feb 2006 03:11:00 -0700 [EMAIL PROTECTED]
Do You have enough pwoer to provide your patrner high quality S-EX on St.Valentine day? Get a MON-STER pwoer, nothing can bring your ererction down! Show your partner the PWOER of your LOEV and she will always remember You. Loev will ALWAYS be associated with YOU! Your order will be PRIVATE, nobody will know what You use. Follow this link and get SSPECIAL DISSCOOUNT for that period: http://vMGlmr0qt8wrsrof3ljm63w8l3l.ottomankd.com/ Oxvxwnrklyuzvs Vooijfslijdh Sat, 04 Feb 2006 03:11:00 -0700 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
