Our Apologies for the Down Time This Weekend (Servercraft Migration)


 
Thread Tools Search this Thread
Contact Us Post Here to Contact Site Administrators and Moderators Our Apologies for the Down Time This Weekend (Servercraft Migration)
# 1  
Old 09-29-2014
Network Our Apologies for the Down Time This Weekend (Servercraft Migration)

In case you did not notice, our server was not available for about 10 hours this weekend. Our service provider (Servercraft) moved their entire data center from Houston to Dallas, TX.

They sent numerous emails to me but because of how I have configured gmail, none of the messages made it to my main inbox and so we missed out on all notices. This is the reason why advance notice was not given to our community and I apologize for that.

I have tried to get our providers to migrate to messaging using LINE or FB (and not email) since I'm not much of an email user these days; but seems many businesses are still "stuck" in the email world for notices. I"m not a big fan of email for notices; and so this is a part of the reason we did not get the notices from Servercraft. Again, my apologies for the downtime this weekend.

The good news is that the data center migration was a success Smilie

Image
Login or Register to Ask a Question

Previous Thread | Next Thread

4 More Discussions You Might Find Interesting

1. AIX

AIX - FC Switch migration, SAN Migration question!

I'm New to AIX / VIOS We're doing a FC switch cutover on an ibm device, connected via SAN. How do I tell if one path to my remote disk is lost? (aix lvm) How do I tell when my link is down on my HBA port? Appreciate your help, very much! (4 Replies)
Discussion started by: BG_JrAdmin
4 Replies

2. UNIX for Dummies Questions & Answers

Apologies from a newbie!

Apologies because this may have been covered elsewhere, but I DID search but couldn't find exactly what I was looking for. My problem is as follows.... I'm doing an extract from an Oracle database, my SQL script does some date manipulation and creates the output file with some date details... (10 Replies)
Discussion started by: speedfreak
10 Replies

3. Post Here to Contact Site Administrators and Moderators

apologies

sorry, I recently posted twice, thinking it didn't go through. didn't mean to make you hassle with redundancy. thanks for your good work. (1 Reply)
Discussion started by: protienplant
1 Replies

4. Post Here to Contact Site Administrators and Moderators

apologies to Perderabo

Sorry Perderabo, really was only asking advice on where best to post, and if I should post. Didn't intend for that missive to be posted. (0 Replies)
Discussion started by: keith.m
0 Replies
Login or Register to Ask a Question
t_sndrel(3)						     Library Functions Manual						       t_sndrel(3)

NAME
t_sndrel() - initiate an orderly release SYNOPSIS
DESCRIPTION
The function is used in connection-oriented mode to initiate an orderly release at a transport endpoint specified by fd, which is a file descriptor previously returned by the function. After this orderly release is indicated, the transport user should not try to send more data through that transport endpoint. An attempt to send more data to a released transport endpoint may block continuously. However, the transport user may continue to receive data over the connection until an orderly release indication is received. This function is an optional service of the transport provider and is only supported if the transport provider returned service type on or Note HP OSI XTI does not support Fork Safety is not fork-safe. RETURN VALUE
Upon successful completion, a value of 0 is returned. Otherwise, a value of -1 is returned and is set to indicate the error. ERRORS
On failure, is set to one of the following: [TBADF] The specified identifier does not refer to a transport endpoint. [TFLOW] Asynchronous mode is indicated because was set, but the transport provider cannot accept a release because of flow-con- trol restrictions. [TLOOK] An asynchronous event has occurred on this transport endpoint and requires immediate attention. [TNOTSUPPORT] This function is not supported by the underlying transport provider. [TSYSERR] A system error has occurred during execution of this function. [TPROTO] (XTI only) This error indicates that a communication problem has been detected between XTI and the transport provider for which there is no other suitable XTI ( SEE ALSO
t_getinfo(3), t_open(3), t_rcvrel(3), thread_safety(5). STANDARDS CONFORMANCE
t_sndrel(3)