Sponsored Content
Special Forums UNIX and Linux Applications Virtualization and Cloud Computing Mini Review: SliceHost v. Linode Customer Service Post 302376134 by Phlak on Monday 30th of November 2009 05:36:06 PM
Old 11-30-2009
Just call your bank and have them reverse the credit card transactions. They usually only require proof that you have attempted to contact the company, and an email will usually cover that. Plus, by reversing this fee, the company is usually charged for a credit card reversal, you can call that getting even.

On the note of SliceHost... I've had a single 512 Slice with them for several months now (6-8?), and love them. Everything you've stated I have also found to be true. Their service is great, customer service is helpful and they are extremely transparent about everything they do.
 

3 More Discussions You Might Find Interesting

1. HP-UX

Customer support engineer

Hi All, I need the help to deploy or implement HP MC service guard 2 node cluster step by step procedure is any1 who can help me to send me the step by step procedure. Thanks and Regards Jahangir (12 Replies)
Discussion started by: Jahangir
12 Replies

2. Virtualization and Cloud Computing

Mini Review: SliceHost v. Linode Ubuntu 9.10 Setup

October 2010 Update: Linode Versus Slicehost – One Year Later A few days ago I posted Mini Review: SliceHost v. Linode Customer Service. At that time, I was going to cancel my account with Linode based on problems during the sign-up period. However, Linode asked me to give them another... (2 Replies)
Discussion started by: Neo
2 Replies

3. Android

Mini Review: Samsung Galaxy S (Android 2.1) v. Nokia E63

Well, I've had my new Galaxy S around one day now and I must say, I am not sure if I regret buying it or not. Before buying it, I read a lot of reviews about the Galaxy S (e.g. Samsung I9000 Galaxy S review: From outer space), including reviews of problems with the GPS and some intermittent WiFi... (6 Replies)
Discussion started by: Neo
6 Replies
pam_authenticate(3)					     Library Functions Manual					       pam_authenticate(3)

NAME
pam_authenticate - perform authentication within the PAM framework SYNOPSIS
[ flag ... ] file ... [ library ... ] DESCRIPTION
is called to authenticate the current user. The user is usually required to enter a password or similar authentication token depending upon the authentication service configured within the system. In the case of smart card authentication this token would be a (Personal Identification Number). The user in question should have been specified by a prior call to or The following flags may be set in the flags field: Authentication service should not generate any messages The authentication service should return if the user has a null authentication token APPLICATION USAGE
Refer to pam(3) for information on thread-safety of PAM interfaces. NOTES
In the case of authentication failures due to an incorrect username or password, it is the responsibility of the application to retry and to maintain the retry count. An authentication service module may implement an internal retry count and return an error if the module does not want the application to retry. If the PAM framework can not load the authentication module, then it will return This indicates a serious failure and that the application should not attempt to retry the authentication. For security reasons, the location of authentication failures is hidden from the user. Thus, if several authentication services are stacked and a single service fails, requires that the user re-authenticate to all the services. A null authentication token in the authentication database will result in successful authentication unless was specified. In such cases, there will not be any prompting for the user to enter an authentication token. The authentication can be done through a smart card. In this case the user plugs their smart card in the smart card reader and is required to enter their smart card PIN. RETURN VALUES
Upon successful completion, is returned. In addition to the error return values described in pam(3), the following values may be returned: Authentication failure. Can not access authentication data due to insufficient credentials. Underlying authentication service can not retrieve authentication information. User not known to the underlying authentication module. An authentication service has maintained a retry count which has been reached. No further retries should be attempted. SEE ALSO
pam(3), pam_start(3), pam_open_session(3), pam_setcred(3). pam_authenticate(3)
All times are GMT -4. The time now is 05:35 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy