<div dir="ltr"><div>okay thanks</div><div><br></div></div><br><div class="gmail_quote"><div class="gmail_attr" dir="ltr">On Tue, Feb 5, 2019 at 5:39 AM filePro <<a href="mailto:filepro.mail@gmail.com">filepro.mail@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid">Copy first and as long as you have the proper fp supplied libraries, fppath and p files it should work...but<br>
some of those files end up in different places depending on the OS layout and the install determines that for you.<br>
So copy first, try filePro, if it doesn't work, do an install which will hurt nothing and fix anything needed.<br>
<br>
Bill<br>
<br>
On 2/4/2019 7:26 PM, scooter6--- via Filepro-list wrote:<br>
> So after the file system change etc<br>
> Can I simply copy the /u directory from existing server to the new server<br>
> or do I need to have fP install media and run fpinstall and then copy data<br>
> files over?<br>
> thanks all<br>
> <br>
> <br>
> On Mon, Feb 4, 2019 at 7:03 PM <a href="mailto:scooter6@gmail.com" target="_blank">scooter6@gmail.com</a> <<a href="mailto:scooter6@gmail.com" target="_blank">scooter6@gmail.com</a>><br>
> wrote:<br>
> <br>
>> haha duly noted Mark<br>
>><br>
>><br>
>> On Mon, Feb 4, 2019 at 6:57 PM Fairlight via Filepro-list <<br>
>> <a href="mailto:filepro-list@lists.celestial.com" target="_blank">filepro-list@lists.celestial.com</a>> wrote:<br>
>><br>
>>> All I can say is that I would never willingly use ext4. It has issues.<br>
>>> Past everything I've said thus far on the matter, you're getting into paid<br>
>>> "re-research the comparisons of merits and detractors between valid<br>
>>> current<br>
>>> filesystems" territory, which is well beyond the scope of this list.<br>
>>><br>
>>> You can totally do whatever you like with it. I'm not being paid to<br>
>>> ensure<br>
>>> it works until OS End-of-Life and possibly beyond, so it's not really my<br>
>>> problem. It's your box to enjoy or suffer through as you see fit. ;)<br>
>>><br>
>>> m-><br>
>>><br>
>>><br>
>>> On Mon, Feb 04, 2019 at 06:44:02PM -0500, <a href="mailto:scooter6@gmail.com" target="_blank">scooter6@gmail.com</a> thus spoke:<br>
>>>> Mark,<br>
>>>> So this really would only apply to the /u filesystem (that is 3.9TB)<br>
>>>> where fP and data will be<br>
>>>> The others can remain ext4 with no issues ? Or just best to convert<br>
>>> all<br>
>>>> ext4 file systems to XFS?<br>
>>>><br>
>>>> On Mon, Feb 4, 2019 at 6:10 PM Fairlight via Filepro-list<br>
>>>> <[1]<a href="mailto:filepro-list@lists.celestial.com" target="_blank">filepro-list@lists.celestial.com</a>> wrote:<br>
>>>><br>
>>>> It really depends whether you're using 64-bit or 32-bit filePro<br>
>>>> binaries.<br>
>>>> If you're using 64-bit, you're fine in any event. If you're using<br>
>>>> 32-bit,<br>
>>>> I suspect you may run into inode number issues. I'd have to look<br>
>>>> up how<br>
>>>> ext4 handles its internal structure, and see if it's BTree+ as well<br>
>>>> in<br>
>>>> order to say definitively. Or do some testing.<br>
>>>> I would -never- willingly recommend ext4. The problem with ext4<br>
>>> is<br>
>>>> that it<br>
>>>> has a static inode table. If you create a filesystem of 'x' size<br>
>>>> (say<br>
>>>> 100GB), by default it allocates 'z' inodes. It's a steady default<br>
>>>> relationship between filesystem size and inode count. Two<br>
>>> problems<br>
>>>> with<br>
>>>> this being static:<br>
>>>> 1) If you use heavily heirarchical filesystem structures for<br>
>>> storage<br>
>>>> of<br>
>>>> data (think postfix-type queues or storage in nested directories),<br>
>>>> you will<br>
>>>> probably exhaust inode space well before you exhaust disk space.Â<br>
>>>> You can<br>
>>>> read 50% disk available, but be out of inodes and will be unable to<br>
>>>> write<br>
>>>> any new files. You can add data to existing files, but once you<br>
>>>> hit the<br>
>>>> inode limit, you're done adding files or directories. Which might<br>
>>>> not be<br>
>>>> so bad, if not for the fact that:<br>
>>>> 2) The inode table is so static that it is immutable, post-mkfs.Â<br>
>>>> It<br>
>>>> cannot be retuned by any means. If you allocate 1TB worth of disk<br>
>>>> to the<br>
>>>> filesystem, then later add 2TB (which it will happily let you do,<br>
>>>> and<br>
>>>> which obviously LVM2 supports with ease), you will -still- only<br>
>>> have<br>
>>>> the<br>
>>>> same quantity of inodes to use under 3TB that you originally had<br>
>>>> under<br>
>>>> 1TB. There is no way around this, short of syncing the entire lot<br>
>>>> to<br>
>>>> another drive, redoing the whole filesystem from scratch with mkfs,<br>
>>>> and<br>
>>>> then syncing everything back. ext4 itself has no inherent<br>
>>>> accomodation for<br>
>>>> increasing the inode table size. None.<br>
>>>> Do yourself a huge favour, and rework it using XFS if you care<br>
>>> about<br>
>>>> maintaining scalability.<br>
>>>> m-><br>
>>>> On Mon, Feb 04, 2019 at 03:08:24PM -0500, [2]<a href="mailto:scooter6@gmail.com" target="_blank">scooter6@gmail.com</a><br>
>>> thus<br>
>>>> spoke:<br>
>>>> >Â Â Just to add - I installed CentOS 7 on RAID 10 hardware RAID<br>
>>>> on the new<br>
>>>> >Â Â Dell PowerEdge<br>
>>>> >Â Â I have the OS installed at this point and this is as far as<br>
>>>> I've gotten<br>
>>>> >Â Â The server has four (4) 2TB NLSAS hot plug hard drives<br>
>>>> >Â Â I installed all filesystems as ext4 -- I allowed Centos to<br>
>>>> partition<br>
>>>> >Â Â automatically this leaves with a 3.9TB /u file system that<br>
>>> is<br>
>>>> ext4<br>
>>>> >Â Â Would you recommend a different filesystem?<br>
>>>> ><br>
>>>> >Â Â On Mon, Feb 4, 2019 at 2:36 PM Scott Walker via Filepro-list<br>
>>>> >Â Â <[1][3]<a href="mailto:filepro-list@lists.celestial.com" target="_blank">filepro-list@lists.celestial.com</a>> wrote:<br>
>>>> ><br>
>>>> >Â Â Â Mark,<br>
>>>> >Â Â Â Brian White was nice enough to help us out with this last<br>
>>>> year.<br>
>>>> >Â Â Â This is from my notes:<br>
>>>> >Â Â Â CentOS Version 7ÃÂ Installation Issues<br>
>>>> >Â Â Â<br>
>>>><br>
>>> --------------------------------------------------------------------<br>
>>>> >Â Â Â --------<br>
>>>> >Â Â Â<br>
>>>> --------------------------------------------------------------<br>
>>>> >Â Â Â You must have libtermcap.so.2 installed!<br>
>>>> >Â Â Â Ã On CentOS 7 you mustÃÂ first install libc.so.6<br>
>>>> >Â Â Â ÃÂ ÃÂ ÃÂ ÃÂ yum install libc.so.6<br>
>>>> >Â Â Â Then install:<br>
>>>> >Â Â Â ÃÂ ÃÂ ÃÂ ÃÂ rpm -ivh<br>
>>>> >Â Â Â compat-libtermcap-2.0.8-50flt.el7.centos.i686.rpm<br>
>>>> >Â Â Â The above file was provided by Brian.ÃÂ I can email you<br>
>>> a<br>
>>>> copy if<br>
>>>> >Â Â Â desired.<br>
>>>> >Â Â Â Regards,<br>
>>>> >Â Â Â Scott Walker<br>
>>>> >Â Â Â [2][4]<a href="mailto:scott.walker@ramsystemscorp.com" target="_blank">scott.walker@ramsystemscorp.com</a><br>
>>>> >Â Â Â -----Original Message-----<br>
>>>> >Â Â Â From: Filepro-list<br>
>>>> >Â Â Â<br>
>>>> [mailto:<br>
>>> [3]filepro-list-bounces+scottwalker=ramsystemscorp.com@lists<br>
>>>> >Â Â Â .celestial.<br>
>>>> >Â Â Â com] On Behalf Of Fairlight via Filepro-list<br>
>>>> >Â Â Â Sent: Monday, February 4, 2019 1:58 PM<br>
>>>> >Â Â Â To: [4][5]<a href="mailto:filepro-list@lists.celestial.com" target="_blank">filepro-list@lists.celestial.com</a><br>
>>>> >Â Â Â Subject: Re: New server migration<br>
>>>> >Â Â Â My previous comments about XFS were for 32-bit<br>
>>>> binaries.ÃÂ The bit<br>
>>>> >Â Â Â depth is<br>
>>>> >Â Â Â important, as even 6.0.0 comes in both 32-bit and<br>
>>>> 64-bit.ÃÂ If<br>
>>>> >Â Â Â you're running<br>
>>>> >Â Â Â 64-bit, you can use inode64 on any filesystem size, and<br>
>>> it<br>
>>>> shouldn't<br>
>>>> >Â Â Â cause<br>
>>>> >Â Â Â issues.<br>
>>>> >Â Â Â If you're running 64-bit binaries, compat-libtermcap may<br>
>>>> still be an<br>
>>>> >Â Â Â issue<br>
>>>> >Â Â Â (probably is).ÃÂ I'd have to revisit that directly to<br>
>>>> confirm or<br>
>>>> >Â Â Â deny.ÃÂ I<br>
>>>> >Â Â Â remember that the i686 architecture build target did not<br>
>>>> exist in<br>
>>>> >Â Â Â the spec<br>
>>>> >Â Â Â file I got from the official SRPM, but that's only<br>
>>>> necessary if you<br>
>>>> >Â Â Â run<br>
>>>> >Â Â Â 32-bit binaries.ÃÂ The package itself likely still needs<br>
>>>> to be built<br>
>>>> >Â Â Â properly, so you're not relying on what I remember as<br>
>>>> being the<br>
>>>> >Â Â Â default<br>
>>>> >Â Â Â broken configuration.<br>
>>>> >Â Â Â m-><br>
>>>> >Â Â Â On Mon, Feb 04, 2019 at 11:02:34AM -0500, scooter6--- via<br>
>>>> >Â Â Â Filepro-list thus<br>
>>>> >Â Â Â spoke:<br>
>>>> >Â Â Â > To clarify, this is with fP 5.6.10R4<br>
>>>> >Â Â Â ><br>
>>>> >Â Â Â ><br>
>>>> >Â Â Â ><br>
>>>> >Â Â Â > On Mon, Feb 4, 2019 at 10:22 AM [5][6]<br>
>>> <a href="mailto:scooter6@gmail.com" target="_blank">scooter6@gmail.com</a><br>
>>>> >Â Â Â > <[6][7]<a href="mailto:scooter6@gmail.com" target="_blank">scooter6@gmail.com</a>><br>
>>>> >Â Â Â > wrote:<br>
>>>> >Â Â Â ><br>
>>>> >Â Â Â > > Just purchased our new Dell PowerEdge server that I<br>
>>>> have<br>
>>>> >Â Â Â installed<br>
>>>> >Â Â Â > > CentOS<br>
>>>> >Â Â Â > > 7 on<br>
>>>> >Â Â Â > ><br>
>>>> >Â Â Â > > Am migrating from older Dell PowerEdge that has<br>
>>> Centos<br>
>>>> 5.10 on<br>
>>>> >Â Â Â it<br>
>>>> >Â Â Â > ><br>
>>>> >Â Â Â > > Is there a 'recipe book' anyone may have on steps to<br>
>>>> migrate all<br>
>>>> >Â Â Â data<br>
>>>> >Â Â Â etc?<br>
>>>> >Â Â Â > > Can a simple copy of the fp directories etc do the<br>
>>>> trick or does<br>
>>>> >Â Â Â the<br>
>>>> >Â Â Â > > new server need to go through fpinstall ?<br>
>>>> >Â Â Â > ><br>
>>>> >Â Â Â > > I know there are significant changes in CentOS from<br>
>>>> 5.10 to 6<br>
>>>> >Â Â Â and<br>
>>>> >Â Â Â > > then to<br>
>>>> >Â Â Â > > 7 but in what I've read I don't think there too much<br>
>>>> of a<br>
>>>> >Â Â Â concern<br>
>>>> >Â Â Â > > for purposes of what we do here<br>
>>>> >Â Â Â > ><br>
>>>> >Â Â Â > > Curious if anyone has done this similar migration and<br>
>>>> what to<br>
>>>> >Â Â Â watch<br>
>>>> >Â Â Â > > out for or best steps in order to make this as<br>
>>>> seamless as<br>
>>>> >Â Â Â possible<br>
>>>> >Â Â Â > ><br>
>>>> >Â Â Â > > Thanks for any insight<br>
>>>> >Â Â Â > ><br>
>>>> >Â Â Â > > Scott<br>
>>>> >Â Â Â > > PDM<br>
>>>> >Â Â Â > ><br>
>>>> >Â Â Â > -------------- next part -------------- An HTML<br>
>>>> attachment was<br>
>>>> >Â Â Â > scrubbed...<br>
>>>> >Â Â Â > URL:<br>
>>>> >Â Â Â ><br>
>>>> >Â Â Â<br>
>>>> <[7][8]<br>
>>> <a href="http://mailman.celestial.com/pipermail/filepro-list/attachmen" target="_blank" rel="noreferrer">http://mailman.celestial.com/pipermail/filepro-list/attachmen</a><br>
>>>> ts/<br>
>>>> >Â Â Â 20190<br>
>>>> >Â Â Â > 204/1b6775da/attachment.html><br>
>>>> >Â Â Â > _______________________________________________<br>
>>>> >Â Â Â > Filepro-list mailing list<br>
>>>> >Â Â Â > [8][9]<a href="mailto:Filepro-list@lists.celestial.com" target="_blank">Filepro-list@lists.celestial.com</a><br>
>>>> >Â Â Â > Subscribe/Unsubscribe/Subscription Changes<br>
>>>> >Â Â Â ><br>
>>>> [9][10]<a href="http://mailman.celestial.com/mailman/listinfo/filepro-list" target="_blank" rel="noreferrer">http://mailman.celestial.com/mailman/listinfo/filepro-list</a><br>
>>>> >Â Â Â ><br>
>>>> >Â Â Â --<br>
>>>> >Â Â Â Audio panton, cogito singularis.<br>
>>>> >Â Â Â _______________________________________________<br>
>>>> >Â Â Â Filepro-list mailing list<br>
>>>> >Â Â Â [10][11]<a href="mailto:Filepro-list@lists.celestial.com" target="_blank">Filepro-list@lists.celestial.com</a><br>
>>>> >Â Â Â Subscribe/Unsubscribe/Subscription Changes<br>
>>>> >Â Â Â<br>
>>>> [11][12]<a href="http://mailman.celestial.com/mailman/listinfo/filepro-list" target="_blank" rel="noreferrer">http://mailman.celestial.com/mailman/listinfo/filepro-list</a><br>
>>>> >Â Â Â _______________________________________________<br>
>>>> >Â Â Â Filepro-list mailing list<br>
>>>> >Â Â Â [12][13]<a href="mailto:Filepro-list@lists.celestial.com" target="_blank">Filepro-list@lists.celestial.com</a><br>
>>>> >Â Â Â Subscribe/Unsubscribe/Subscription Changes<br>
>>>> >Â Â Â<br>
>>>> [13][14]<a href="http://mailman.celestial.com/mailman/listinfo/filepro-list" target="_blank" rel="noreferrer">http://mailman.celestial.com/mailman/listinfo/filepro-list</a><br>
>>>> ><br>
>>>> > References<br>
>>>> ><br>
>>>> >Â Â 1. mailto:[15]<a href="mailto:filepro-list@lists.celestial.com" target="_blank">filepro-list@lists.celestial.com</a><br>
>>>> >Â Â 2. mailto:[16]<a href="mailto:scott.walker@ramsystemscorp.com" target="_blank">scott.walker@ramsystemscorp.com</a><br>
>>>> >Â Â 3. mailto:[17]filepro-list-bounces%2Bscottwalker<br>
>>>> >Â Â 4. mailto:[18]<a href="mailto:filepro-list@lists.celestial.com" target="_blank">filepro-list@lists.celestial.com</a><br>
>>>> >Â Â 5. mailto:[19]<a href="mailto:scooter6@gmail.com" target="_blank">scooter6@gmail.com</a><br>
>>>> >Â Â 6. mailto:[20]<a href="mailto:scooter6@gmail.com" target="_blank">scooter6@gmail.com</a><br>
>>>> >Â Â 7.<br>
>>>> [21]<br>
>>> <a href="http://mailman.celestial.com/pipermail/filepro-list/attachments/" target="_blank" rel="noreferrer">http://mailman.celestial.com/pipermail/filepro-list/attachments/</a><br>
>>>> 20190<br>
>>>> >Â Â 8. mailto:[22]<a href="mailto:Filepro-list@lists.celestial.com" target="_blank">Filepro-list@lists.celestial.com</a><br>
>>>> >Â Â 9.<br>
>>>> [23]<a href="http://mailman.celestial.com/mailman/listinfo/filepro-list" target="_blank" rel="noreferrer">http://mailman.celestial.com/mailman/listinfo/filepro-list</a><br>
>>>> >Â Â 10. mailto:[24]<a href="mailto:Filepro-list@lists.celestial.com" target="_blank">Filepro-list@lists.celestial.com</a><br>
>>>> >Â Â 11.<br>
>>>> [25]<a href="http://mailman.celestial.com/mailman/listinfo/filepro-list" target="_blank" rel="noreferrer">http://mailman.celestial.com/mailman/listinfo/filepro-list</a><br>
>>>> >Â Â 12. mailto:[26]<a href="mailto:Filepro-list@lists.celestial.com" target="_blank">Filepro-list@lists.celestial.com</a><br>
>>>> >Â Â 13.<br>
>>>> [27]<a href="http://mailman.celestial.com/mailman/listinfo/filepro-list" target="_blank" rel="noreferrer">http://mailman.celestial.com/mailman/listinfo/filepro-list</a><br>
>>>> --<br>
>>>> Audio panton, cogito singularis.<br>
>>>> _______________________________________________<br>
>>>> Filepro-list mailing list<br>
>>>> [28]<a href="mailto:Filepro-list@lists.celestial.com" target="_blank">Filepro-list@lists.celestial.com</a><br>
>>>> Subscribe/Unsubscribe/Subscription Changes<br>
>>>> [29]<a href="http://mailman.celestial.com/mailman/listinfo/filepro-list" target="_blank" rel="noreferrer">http://mailman.celestial.com/mailman/listinfo/filepro-list</a><br>
>>>><br>
>>>> References<br>
>>>><br>
>>>> 1. mailto:<a href="mailto:filepro-list@lists.celestial.com" target="_blank">filepro-list@lists.celestial.com</a><br>
>>>> 2. mailto:<a href="mailto:scooter6@gmail.com" target="_blank">scooter6@gmail.com</a><br>
>>>> 3. mailto:<a href="mailto:filepro-list@lists.celestial.com" target="_blank">filepro-list@lists.celestial.com</a><br>
>>>> 4. mailto:<a href="mailto:scott.walker@ramsystemscorp.com" target="_blank">scott.walker@ramsystemscorp.com</a><br>
>>>> 5. mailto:<a href="mailto:filepro-list@lists.celestial.com" target="_blank">filepro-list@lists.celestial.com</a><br>
>>>> 6. mailto:<a href="mailto:scooter6@gmail.com" target="_blank">scooter6@gmail.com</a><br>
>>>> 7. mailto:<a href="mailto:scooter6@gmail.com" target="_blank">scooter6@gmail.com</a><br>
>>>> 8. <a href="http://mailman.celestial.com/pipermail/filepro-list/attachments/" target="_blank" rel="noreferrer">http://mailman.celestial.com/pipermail/filepro-list/attachments/</a><br>
>>>> 9. mailto:<a href="mailto:Filepro-list@lists.celestial.com" target="_blank">Filepro-list@lists.celestial.com</a><br>
>>>> 10. <a href="http://mailman.celestial.com/mailman/listinfo/filepro-list" target="_blank" rel="noreferrer">http://mailman.celestial.com/mailman/listinfo/filepro-list</a><br>
>>>> 11. mailto:<a href="mailto:Filepro-list@lists.celestial.com" target="_blank">Filepro-list@lists.celestial.com</a><br>
>>>> 12. <a href="http://mailman.celestial.com/mailman/listinfo/filepro-list" target="_blank" rel="noreferrer">http://mailman.celestial.com/mailman/listinfo/filepro-list</a><br>
>>>> 13. mailto:<a href="mailto:Filepro-list@lists.celestial.com" target="_blank">Filepro-list@lists.celestial.com</a><br>
>>>> 14. <a href="http://mailman.celestial.com/mailman/listinfo/filepro-list" target="_blank" rel="noreferrer">http://mailman.celestial.com/mailman/listinfo/filepro-list</a><br>
>>>> 15. mailto:<a href="mailto:filepro-list@lists.celestial.com" target="_blank">filepro-list@lists.celestial.com</a><br>
>>>> 16. mailto:<a href="mailto:scott.walker@ramsystemscorp.com" target="_blank">scott.walker@ramsystemscorp.com</a><br>
>>>> 17. mailto:<a href="mailto:filepro-list-bounces%25252Bscottwalker" target="_blank">filepro-list-bounces%252Bscottwalker</a><br>
>>>> 18. mailto:<a href="mailto:filepro-list@lists.celestial.com" target="_blank">filepro-list@lists.celestial.com</a><br>
>>>> 19. mailto:<a href="mailto:scooter6@gmail.com" target="_blank">scooter6@gmail.com</a><br>
>>>> 20. mailto:<a href="mailto:scooter6@gmail.com" target="_blank">scooter6@gmail.com</a><br>
>>>> 21.<br>
>>> <a href="http://mailman.celestial.com/pipermail/filepro-list/attachments/20190" target="_blank" rel="noreferrer">http://mailman.celestial.com/pipermail/filepro-list/attachments/20190</a><br>
>>>> 22. mailto:<a href="mailto:Filepro-list@lists.celestial.com" target="_blank">Filepro-list@lists.celestial.com</a><br>
>>>> 23. <a href="http://mailman.celestial.com/mailman/listinfo/filepro-list" target="_blank" rel="noreferrer">http://mailman.celestial.com/mailman/listinfo/filepro-list</a><br>
>>>> 24. mailto:<a href="mailto:Filepro-list@lists.celestial.com" target="_blank">Filepro-list@lists.celestial.com</a><br>
>>>> 25. <a href="http://mailman.celestial.com/mailman/listinfo/filepro-list" target="_blank" rel="noreferrer">http://mailman.celestial.com/mailman/listinfo/filepro-list</a><br>
>>>> 26. mailto:<a href="mailto:Filepro-list@lists.celestial.com" target="_blank">Filepro-list@lists.celestial.com</a><br>
>>>> 27. <a href="http://mailman.celestial.com/mailman/listinfo/filepro-list" target="_blank" rel="noreferrer">http://mailman.celestial.com/mailman/listinfo/filepro-list</a><br>
>>>> 28. mailto:<a href="mailto:Filepro-list@lists.celestial.com" target="_blank">Filepro-list@lists.celestial.com</a><br>
>>>> 29. <a href="http://mailman.celestial.com/mailman/listinfo/filepro-list" target="_blank" rel="noreferrer">http://mailman.celestial.com/mailman/listinfo/filepro-list</a><br>
>>><br>
>>> --<br>
>>> Audio panton, cogito singularis.<br>
>>> _______________________________________________<br>
>>> Filepro-list mailing list<br>
>>> <a href="mailto:Filepro-list@lists.celestial.com" target="_blank">Filepro-list@lists.celestial.com</a><br>
>>> Subscribe/Unsubscribe/Subscription Changes<br>
>>> <a href="http://mailman.celestial.com/mailman/listinfo/filepro-list" target="_blank" rel="noreferrer">http://mailman.celestial.com/mailman/listinfo/filepro-list</a><br>
>>><br>
>><br>
> -------------- next part --------------<br>
> An HTML attachment was scrubbed...<br>
> URL: <<a href="http://mailman.celestial.com/pipermail/filepro-list/attachments/20190204/c584f14f/attachment.html" target="_blank" rel="noreferrer">http://mailman.celestial.com/pipermail/filepro-list/attachments/20190204/c584f14f/attachment.html</a>><br>
> _______________________________________________<br>
> Filepro-list mailing list<br>
> <a href="mailto:Filepro-list@lists.celestial.com" target="_blank">Filepro-list@lists.celestial.com</a><br>
> Subscribe/Unsubscribe/Subscription Changes<br>
> <a href="http://mailman.celestial.com/mailman/listinfo/filepro-list" target="_blank" rel="noreferrer">http://mailman.celestial.com/mailman/listinfo/filepro-list</a><br>
> <br>
<br>
---<br>
This email has been checked for viruses by Avast antivirus software.<br>
<a href="https://www.avast.com/antivirus" target="_blank" rel="noreferrer">https://www.avast.com/antivirus</a><br>
<br>
</blockquote></div>