>I still cannot run the ScheduleCron module at all without it running 
away...

There should be no longer any issue with the Schedule::Cron (version >= 
1.01) module since 2.4.5 15162, even the assp installation follows not the 
roadmap.

Thomas



Von:    "William L. Thomson Jr." <[email protected]>
An:     For Users of ASSP <[email protected]>
Datum:  06.07.2015 17:29
Betreff:        Re: [Assp-user] Is this a ASSP issue or Perl version 
issue?



On Thursday, July 02, 2015 12:28:34 PM Jay wrote:
> 
> So my question is this, has anyone else run into this situation?

I have not run into what you describe specifically. But I have had a 
variety of 
odd and other issues that stem from Perl updates, either to perl itself 
and/or 
modules. Going back to December 2014. Prior to that, and having been 
running 
ASSP 3972 hours as of today. I have never had issues with ASSP or Perl as 
I 
have in the last 6+ months.

> Would an update to Perl resolve some of these weird issues?

In my case since updates did cause things to break, like forcing me to 
switch 
to ASSP v2 from v1 due to changes in Perl, not modules. However since then 
I 
have still had a variety of issues. I have recompiled and reinstalled perl 
and 
all modules more than once. Sometimes seems to help, but not sure if it is 

really fixing the problem, or just making me feel better.

That was when I upgraded from Perl 5.12.4 to 5.18.2 on 11/30/2014. 
Recompiled 
that and all perl modules on 12/5/2014. Upgraded to 5.20.1 on 1/26/2015. 
Then 
to 5.20.2 on 2/22/2015. Recompiled that due to a Gentoo update on 
5/17/2015. I 
have rebuild all modules a few times in that period.

> The concern I have
> is if I update Perl, what version should I update to that would not
> cause too many issues, and what I mean by that is concerned about
> breaking modules in ASSP. 

No clue that is anyones guess, only one way to find out really. Just make 
backups in case you need to revert.

> Anyone running a newer version of Perl?

Yes, I am on 5.20.2, and ran versions in between that, and 5.12.4, 5.18.x 
versions. I never ran 5.16.

> How difficult was it to update? 

I have ASSP running on Gentoo, so just did a regular routine update. Which 
I 
have re-done re-compiling and installing perl and all modules at least 4 
or 5 
times in the last 6 months.

> I just want to plan for down time if this is
> the way to go. I have to let my users know.

I did not have any issues from updates immediately. Any issues came up 
later 
on as some oddity. If you update perl and have some issue, it should occur 

right away. Though if not you might have other issues down the road. That 
is 
hard to say, as I still experience some of them at times. But things have 
been 
good for a few weeks. However I did recompile and reinstall perl and all 
modules as of 6/22/2015.

I am running ASSP v2.4.3(15959) since 4/14/2015. I had tried to run it a 
few 
times before but had to revert back to  ASSP v2.4.3(15975) a couple times. 
Its 
been an interesting year with ASSP and Perl...

I blame Perl more than ASSP, as again things were fine till November when 
I did 
a perl update, broke v1, and have been having odd issues with v2 since. I 
still cannot run the ScheduleCron module at all without it running away...

-- 
William L. Thomson Jr.
Obsidian-Studios, Inc.
http://www.obsidian-studios.com

------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
Assp-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-user






DISCLAIMER:
*******************************************************
This email and any files transmitted with it may be confidential, legally 
privileged and protected in law and are intended solely for the use of the 

individual to whom it is addressed.
This email was multiple times scanned for viruses. There should be no 
known virus in this email!
*******************************************************

------------------------------------------------------------------------------
_______________________________________________
Assp-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-user

Reply via email to