dbTalk Databases Forums  

Best workaround for bootup 'respawning too rapidly' for each d3 line in inittab?

comp.databases.pick comp.databases.pick


Discuss Best workaround for bootup 'respawning too rapidly' for each d3 line in inittab? in the comp.databases.pick forum.



Reply
 
Thread Tools Display Modes
  #11  
Old   
Tony Gravagno
 
Posts: n/a

Default Re: Best workaround for bootup 'respawning too rapidly' for each d3 line in inittab? - 10-20-2010 , 12:26 AM






To keep focused on the original question, I'm sorry but I'm unaware of
any documentation for addressing the specific problem described. I
didn't mean to imply that there is a well known solution that you're
missing - the solution is almost certainly buried in CDP archives. My
intent was, that IIRC, this was a FAQ some years ago, and TL support
has undoubtedly addressed it before, so people there almost certainly
have the answer.

I don't have any beefs with you, Frank. I could have just said "try
TL Support" or (to everyone's joy) I could have said nothing at all.
My general lament is that this market loses lots of end-users to
competing platforms, and we don't get enough new ones to replace them.
The DBMS vendors have a respectable hands-off policy with their
resellers, but many resellers simply aren't providing enough value-add
to hold on to the end-users. It's my opinion that the DBMS vendors
should protect their assets by maintaining high standards in their
downline, and ensure that some agency is going to address all needs
and answer all questions for the end-users. That's just one man's
opinion and apparently there are other opinions.

T

Reply With Quote
  #12  
Old   
Tony Gravagno
 
Posts: n/a

Default Re: Best workaround for bootup 'respawning too rapidly' for each d3 line in inittab? - 10-20-2010 , 12:26 AM






"frosty" wrote:

Quote:
Tony Gravagno writed:
You've defined exactly what causes people migrate away from this
market. It's amazing that people get paid a DBMS commission for this
sort of "value-add" service. Holy Toledo.

Nice flame... exactly to whom is this directed? The group?
JETman:
Talk to an end-user who has migrated or is about to migrate, and you
will probably find their reseller follows policies like those
described. I can't tell you how many times I hear people say "I wish
I had known [...whatever we just discussed...] a few months ago, but
it's too late now and the decision has already been made to migrate."
The flame is directed at anyone who follows those policies as a matter
of regular business. Then again, as flames go this was hardly even
luke warm.

If "you" (whomever is reading this) are taking care of your clients,
providing support, and passing issues up the channel, then no, none of
this applies to you, so please don't feel offended.

T

Reply With Quote
  #13  
Old   
Frank Winans
 
Posts: n/a

Default Re: Best workaround for bootup 'respawning too rapidly' for each d3 line in inittab? - 10-20-2010 , 08:27 AM



"Tony Gravagno" wrote
Quote:
To keep focused on the original question, I'm sorry but I'm unaware of
any documentation for addressing the specific problem described. I
didn't mean to imply that there is a well known solution that you're
missing - the solution is almost certainly buried in CDP archives. My
intent was, that IIRC, this was a FAQ some years ago, and TL support
has undoubtedly addressed it before, so people there almost certainly
have the answer.

I don't have any beefs with you, Frank. I could have just said "try
TL Support" or (to everyone's joy) I could have said nothing at all.
My general lament is that this market loses lots of end-users to
competing platforms, and we don't get enough new ones to replace them.
The DBMS vendors have a respectable hands-off policy with their
resellers, but many resellers simply aren't providing enough value-add
to hold on to the end-users. It's my opinion that the DBMS vendors
should protect their assets by maintaining high standards in their
downline, and ensure that some agency is going to address all needs
and answer all questions for the end-users. That's just one man's
opinion and apparently there are other opinions.

T
And I take no offence whatsoever. I also suspect you're flinching over
a similar but now-resolved respawning debacle of yore. I was a bit
impudent to even invite remarks on readers' own reactions to this dgap
settling interval causing messages just after linux bootup, but felt that
maybe it wouldn't matter so much if the days when serial was king are
so far behind us. In no way did I want anyone else to do my homework
for me, or disclose technology their employers would object to. My
curiosity just got away from me, there...

Thanks for all the posts you've made over the years; not just Tony
but all you others, too.
Erm, except you dweebs in my killfile ;-)

Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.