Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*amanda\-2\.5\.2p1\s+on\s+SCO\s+5\.0\.4\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*amanda\-2\.5\.2p1\s+on\s+SCO\s+5\.0\.4\s*$/: 7 ]

Total 7 documents matching your query.

1. Re: amanda-2.5.2p1 on SCO 5.0.4 (score: 1): Author: "Dustin J. Mitchell" <dustin AT zmanda DOT com>; Date: Wed, 1 Oct 2008 13:13:27 -0400; OK, folks, this thread has been a while coming, but I wanted to mention that it's been fixed. We discovered that on Michael's system, in whatever context amandad runs, isspace(0x20) == 0. That is to; /usr/local/webapp/mharc-adsm.org/html/Amanda-Users/2008-10/msg00005.html (11,401 bytes)
2. amanda-2.5.2p1 on SCO 5.0.4 (score: 1): Author: Michael Reuland <michael.reuland AT activant DOT com>; Date: Mon, 21 Jul 2008 11:24:23 -0500; I trying to run Amanda-2.5.2p1 on an SCO OpenServer 5.0.4 system compiled with gcc-3.4.4 I've worked out the dependencies and syntax errors in the builds to get the binary files compiled. My problem; /usr/local/webapp/mharc-adsm.org/html/Amanda-Users/2008-07/msg00109.html (21,788 bytes)
3. Re: amanda-2.5.2p1 on SCO 5.0.4 (score: 1): Author: "Dustin J. Mitchell" <dustin AT zmanda DOT com>; Date: Mon, 21 Jul 2008 14:12:13 -0400; This is basically a protocol error -- the server connected to the client, expecting a binary-formatted packet in response, but the config parser output an error message over the socket instead. Runni; /usr/local/webapp/mharc-adsm.org/html/Amanda-Users/2008-07/msg00111.html (14,278 bytes)
4. Re: amanda-2.5.2p1 on SCO 5.0.4 (score: 1): Author: Kenneth Berry <kberry AT microbeef DOT com>; Date: Mon, 21 Jul 2008 16:56:47 -0500; Sent from my iPhone On Jul 21, 2008, at 1:12 PM, "Dustin J. Mitchell" <dustin AT zmanda DOT com> wrote: On Mon, Jul 21, 2008 at 12:24 PM, Michael Reuland <michael.reuland AT activant DOT com> wrote:; /usr/local/webapp/mharc-adsm.org/html/Amanda-Users/2008-07/msg00113.html (15,074 bytes)
5. Re: amanda-2.5.2p1 on SCO 5.0.4 (score: 1): Author: Michael Reuland <michael.reuland AT activant DOT com>; Date: Wed, 23 Jul 2008 13:38:23 -0500; I have tried several configuration changes and still end up w/ the same problem. After each change I have returned to the original configuration to try and keep things in order. I'm still getting the; /usr/local/webapp/mharc-adsm.org/html/Amanda-Users/2008-07/msg00141.html (17,470 bytes)
6. Re: amanda-2.5.2p1 on SCO 5.0.4 (score: 1): Author: "Michael Reuland" <michael.reuland AT activant DOT com>; Date: Wed, 23 Jul 2008 15:37:56 -0500; If the configuration keywords are shifted into different order, the amcheck still reports the problem at the first line that has any keyword. If I insert an invalid configuration keyword, the amcheck; /usr/local/webapp/mharc-adsm.org/html/Amanda-Users/2008-07/msg00146.html (18,038 bytes)
7. Re: amanda-2.5.2p1 on SCO 5.0.4 (score: 1): Author: "Dustin J. Mitchell" <dustin AT zmanda DOT com>; Date: Wed, 23 Jul 2008 15:02:03 -0400; What happens if you switch the order of lines so that the first line is e.g., the second? You can run 'amrecover' on the client. It should give the same error messages. On a completely unrelated topi; /usr/local/webapp/mharc-adsm.org/html/Amanda-Users/2008-07/msg00152.html (12,430 bytes)

Current List: 1 - 7
Page: [1]