Sponsored Content
Full Discussion: Getting error
Top Forums UNIX for Dummies Questions & Answers Getting error Post 302180135 by era on Sunday 30th of March 2008 04:06:46 AM
Old 03-30-2008
Good question. You could say you want what Dreamhost offers and see how they react. Sounds like a small shop who might be willing to tweak their system in order to keep you as a customer. Also sounds like they don't have any SSI facility at all at the moment, otherwise they'd just point you to its documentation.

This is all a bit mysterious; I have a nagging doubt that you will tell us in the end that the reason you want this for i X and we'd all jump and shout and point you to the web site where you can get that.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Error: Internal system error: Unable to initialize standard output file

Hey guys, need some help. Running AIX Version 5.2 and one of our cron jobs is writing errors to a log file. Any ideas on the following error message. Error: Internal system error: Unable to initialize standard output file I'm guessing more info might be needed, so let me know. Thanks (2 Replies)
Discussion started by: firkus
2 Replies

2. UNIX for Dummies Questions & Answers

awk Shell Script error : "Syntax Error : `Split' unexpected

hi there i write one awk script file in shell programing the code is related to dd/mm/yy to month, day year format but i get an error please can anybody help me out in this problem ?????? i give my code here including error awk ` # date-month -- convert mm/dd/yy to month day,... (2 Replies)
Discussion started by: Herry
2 Replies

3. UNIX for Advanced & Expert Users

VSI-FAX error - Cannot login to server and Connecto error to host

I encounters a VSIFAX related error: vfxstat: Cannot login to server on rsac3: Connect error to host 172.16.1.45: Invalid argument It started happening last night with a core dump. Then we can't start VSIFAX again. I am runing VSI-FAX 4.2 on AIX box (0 Replies)
Discussion started by: b_jin
0 Replies

4. AIX

nim mksysb error :/usr/bin/savevg[33]: 1016,07: syntax error

-------------------------------------------------------------------------------- Hello, help me please. I am trying to create a mksysb bakup using nim. I am geting this error, how to correct it ? : Command : failed stdout: yes stderr: no... (9 Replies)
Discussion started by: astjen
9 Replies

5. Solaris

fssnap error :snapshot error: File system could not be write locked

Hi Guys. This is part of my filesystem structure : Filesystem size used avail capacity Mounted on /dev/md/dsk/d0 47G 5.2G 42G 12% / /devices 0K 0K 0K 0% /devices ctfs 0K 0K 0K 0% ... (2 Replies)
Discussion started by: aggadtech08
2 Replies

6. UNIX for Advanced & Expert Users

ssh error: Error reading response length from authentication socket

Hi - I am getting the error `Error reading response length from authentication socket' when I ssh from my cluster to another cluster, and then back to my cluster. It doesn't seem to affect anything, but it's just annoying that it always pops up and tends to confuse new users of the cluster. I... (1 Reply)
Discussion started by: cpp6f
1 Replies

7. UNIX for Dummies Questions & Answers

> 5 ")syntax error: operand expected (error token is " error

im kinda new to shell scripting so i need some help i try to run this script and get the error code > 5 ")syntax error: operand expected (error token is " the code for the script is #!/bin/sh # # script to see if the given value is correct # # Define errors ER_AF=86 # Var is... (4 Replies)
Discussion started by: metal005
4 Replies

8. Shell Programming and Scripting

What is this error log = hda: irq timeout: error=0x00 and how to solve?

what is this error log = hda: irq timeout: error=0x00 and how to solve? every day upon checking the logs i see this error. hda: irq timeout: error=0x00 hda: irq timeout: error=0x00 hda: irq timeout: error=0x00 hda: irq timeout: error=0x00 hw_client: segfault at 0000000000000046 rip... (3 Replies)
Discussion started by: avtalan
3 Replies

9. Solaris

Rpcinfo: can't contact portmapper: RPC: Authentication error; why = Failed (unspecified error)

I have two servers with a fresh install of Solaris 11, and having problems when doing rpcinfo between them. There is no firewall involved, so everything should theoretically be getting through. Does anyone have any ideas? I did a lot of Google searches, and haven't found a working solution yet. ... (2 Replies)
Discussion started by: christr
2 Replies

10. UNIX for Beginners Questions & Answers

Print Error in Console and both Error & Output in Log file - UNIX

I am writing a shell script with 2 run time arguments. During the execution if i got any error, then it needs to redirected to a error file and in console. Also both error and output to be redirected to a log file. But i am facing the below error. #! /bin/sh errExit () { errMsg=`cat... (1 Reply)
Discussion started by: sarathy_a35
1 Replies
QAsciiCacheIterator(3qt)												  QAsciiCacheIterator(3qt)

NAME
QAsciiCacheIterator - Iterator for QAsciiCache collections SYNOPSIS
#include <qasciicache.h> Public Members QAsciiCacheIterator ( const QAsciiCache<type> & cache ) QAsciiCacheIterator ( const QAsciiCacheIterator<type> & ci ) QAsciiCacheIterator<type> & operator= ( const QAsciiCacheIterator<type> & ci ) uint count () const bool isEmpty () const bool atFirst () const bool atLast () const type * toFirst () type * toLast () operator type * () const type * current () const const char * currentKey () const type * operator() () type * operator++ () type * operator+= ( uint jump ) type * operator-- () type * operator-= ( uint jump ) DESCRIPTION
The QAsciiCacheIterator class provides an iterator for QAsciiCache collections. Note that the traversal order is arbitrary; you are not guaranteed any particular order. If new objects are inserted into the cache while the iterator is active, the iterator may or may not see them. Multiple iterators are completely independent, even when they operate on the same QAsciiCache. QAsciiCache updates all iterators that refer an item when that item is removed. QAsciiCacheIterator provides an operator++() and an operator+=() to traverse the cache; current() and currentKey() to access the current cache item and its key. It also provides atFirst() and atLast(), which return TRUE if the iterator points to the first or last item in the cache respectively. The isEmpty() function returns TRUE if the cache is empty; and count() returns the number of items in the cache. Note that atFirst() and atLast() refer to the iterator's arbitrary ordering, not to the cache's internal least recently used list. See also QAsciiCache, Collection Classes, and Non-GUI Classes. MEMBER FUNCTION DOCUMENTATION
QAsciiCacheIterator::QAsciiCacheIterator ( const QAsciiCache<type> & cache ) Constructs an iterator for cache. The current iterator item is set to point to the first item in the cache. QAsciiCacheIterator::QAsciiCacheIterator ( const QAsciiCacheIterator<type> & ci ) Constructs an iterator for the same cache as ci. The new iterator starts at the same item as ci.current() but moves independently from there on. bool QAsciiCacheIterator::atFirst () const Returns TRUE if the iterator points to the first item in the cache; otherwise returns FALSE. Note that this refers to the iterator's arbitrary ordering, not to the cache's internal least recently used list. See also toFirst() and atLast(). bool QAsciiCacheIterator::atLast () const Returns TRUE if the iterator points to the last item in the cache; otherwise returns FALSE. Note that this refers to the iterator's arbitrary ordering, not to the cache's internal least recently used list. See also toLast() and atFirst(). uint QAsciiCacheIterator::count () const Returns the number of items in the cache over which this iterator operates. See also isEmpty(). type * QAsciiCacheIterator::current () const Returns a pointer to the current iterator item. const char * QAsciiCacheIterator::currentKey () const Returns the key for the current iterator item. bool QAsciiCacheIterator::isEmpty () const Returns TRUE if the cache is empty, i.e. count() == 0; otherwise returns FALSE. See also count(). QAsciiCacheIterator::operator type * () const Cast operator. Returns a pointer to the current iterator item. Same as current(). type * QAsciiCacheIterator::operator() () Makes the succeeding item current and returns the original current item. If the current iterator item was the last item in the cache or if it was 0, 0 is returned. type * QAsciiCacheIterator::operator++ () Prefix ++ makes the iterator point to the item just after current(), and makes that the new current item for the iterator. If current() was the last item, operator++() returns 0. type * QAsciiCacheIterator::operator+= ( uint jump ) Returns the item jump positions after the current item, or 0 if it is beyond the last item. Makes this the current item. type * QAsciiCacheIterator::operator-- () Prefix -- makes the iterator point to the item just before current(), and makes that the new current item for the iterator. If current() was the first item, operator--() returns 0. type * QAsciiCacheIterator::operator-= ( uint jump ) Returns the item jump positions before the current item, or 0 if it is before the first item. Makes this the current item. QAsciiCacheIterator<;type> & QAsciiCacheIterator::operator= ( const QAsciiCacheIterator<type> & ci ) Makes this an iterator for the same cache as ci. The new iterator starts at the same item as ci.current(), but moves independently thereafter. type * QAsciiCacheIterator::toFirst () Sets the iterator to point to the first item in the cache and returns a pointer to the item. Sets the iterator to 0 and returns 0 if the cache is empty. See also toLast() and isEmpty(). type * QAsciiCacheIterator::toLast () Sets the iterator to point to the last item in the cache and returns a pointer to the item. Sets the iterator to 0 and returns 0 if the cache is empty. See also isEmpty(). SEE ALSO
http://doc.trolltech.com/qasciicacheiterator.html http://www.trolltech.com/faq/tech.html COPYRIGHT
Copyright 1992-2007 Trolltech ASA, http://www.trolltech.com. See the license file included in the distribution for a complete license statement. AUTHOR
Generated automatically from the source code. BUGS
If you find a bug in Qt, please report it as described in http://doc.trolltech.com/bughowto.html. Good bug reports help us to help you. Thank you. The definitive Qt documentation is provided in HTML format; it is located at $QTDIR/doc/html and can be read using Qt Assistant or with a web browser. This man page is provided as a convenience for those users who prefer man pages, although this format is not officially supported by Trolltech. If you find errors in this manual page, please report them to qt-bugs@trolltech.com. Please include the name of the manual page (qasciicacheiterator.3qt) and the Qt version (3.3.8). Trolltech AS 2 February 2007 QAsciiCacheIterator(3qt)
All times are GMT -4. The time now is 07:13 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy