Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Bacula\-users\]\s+Config\s+token\s+too\s+long\s+\-\s+limit\s+of\s+500\s+characters\?\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Bacula\-users\]\s+Config\s+token\s+too\s+long\s+\-\s+limit\s+of\s+500\s+characters\?\s*$/: 2 ]

Total 2 documents matching your query.

1. [Bacula-users] Config token too long - limit of 500 characters? (score: 1): Author: Dan Langille <dan AT langille DOT org>; Date: Sun, 23 Mar 2014 14:53:38 -0400; For the record, given that Ive found this error in the archives and did not find the answer. I was working on a COPY job today, expanding the SQL to help with some testing. I have encountered the con; /usr/local/webapp/mharc-adsm.org/html/Bacula-users/2014-03/msg00146.html (13,034 bytes)
2. Re: [Bacula-users] Config token too long - limit of 500 characters? (score: 1): Author: Kern Sibbald <kern AT sibbald DOT com>; Date: Mon, 24 Mar 2014 07:47:40 +0100; --BEGIN PGP SIGNED MESSAGE-- Hash: SHA1 Hello Dan, This restriction has been removed in version 7.0.0, which will be ready in about a week. There just remains compatibility testing (being done by Bac; /usr/local/webapp/mharc-adsm.org/html/Bacula-users/2014-03/msg00150.html (16,199 bytes)

Current List: 1 - 2
Page: [1]