04-30-2014
Thanks Don...
I thought "base 68" looked more than ludicrous.
I never dreamt of "D" being a hex digit however; I just assumed it was a literal ASCII to decimal conversion...
9 More Discussions You Might Find Interesting
1. AIX
How to replace many numbers with one number in a file.
Many numbers like 444565,454678,443298,etc. i want to replace these with one number (300).Please halp me out. (2 Replies)
Discussion started by: vpandey
2 Replies
2. Programming
Hi all,
I need to change the source port number of an outgoing TCP packet. First I have to bind the socket to a particular port(suppose 9001) but when I send the TCP packet I want to change the source port number lets say to 9002 still letting the socket to be bound to the same old port (9001).... (0 Replies)
Discussion started by: anuragrai134
0 Replies
3. UNIX for Dummies Questions & Answers
Hi,
My requirement is I have an input file with a continuous series from 10000 to 99999. I have some numbers missing from those series. I want a output file which produces those missing numbers.
Eg: 10002, 99999 are missing from the series then the output file should contain those... (4 Replies)
Discussion started by: rakeshbharadwaj
4 Replies
4. Shell Programming and Scripting
Hello All,
I am having problem to find what is the smallest number from 90% of highest numbers from all numbers in file. I am having file with thousands of lines and hundreds of columns.
I am familiar mainly with bash but I am open to whatever suggestion witch will lead to the solutions.
If I... (11 Replies)
Discussion started by: Apfik
11 Replies
5. Shell Programming and Scripting
out of a range of numbers, how can i pick out the number that is the closest to any arbitrary/random number that a user supplies?
say the range of numbers are between 1 - 90000. but that doesn't mean each number exist between 1 - 90000. the range of numbers could be for example:
1, 3, 4, 6,... (6 Replies)
Discussion started by: SkySmart
6 Replies
6. Shell Programming and Scripting
Hi All,
I am stuck with this problem.
I have some 100000 (.dat) 1.dat, 2.dat,3.dat etc until 100000.dat files which look like this:
1.dat
1
2
3
4
0.99
4.54
All my files 1.dat until 100000.dat look the same but with different numbers.
I have to first add all the numbers in each... (1 Reply)
Discussion started by: shoaibjameel123
1 Replies
7. Shell Programming and Scripting
Hi,
I want to remove the following code from Source files (or replace the code with empty.) from all the source files in given directory.
finally {
if (null != hibernateSession && hibernateSession.isOpen()) {
//hibernateSession.close();
}
}
It would be great if the script has... (2 Replies)
Discussion started by: hareeshram
2 Replies
8. Shell Programming and Scripting
Hi, I have a list.txt file with number ranges and want to print/save new all.txt file with all the numbers and between the numbers.
== list.txt ==
65936
65938
65942 && 65943
65945 ... (7 Replies)
Discussion started by: AK47
7 Replies
9. Shell Programming and Scripting
Hi Guys,
how to count number of files successfully copied while coping files from source to destination path
ex:10 files from source to target location copying
if 8 files copied successfully then
echo successfully copied=8
failure=2 files
if two files get error to coping files from... (23 Replies)
Discussion started by: sravanreddy
23 Replies
LEARN ABOUT DEBIAN
ipsec_atoul
IPSEC_ATOUL(3) 11 June 2001 IPSEC_ATOUL(3)
NAME
ipsec_atoul, ipsec_ultoa - convert unsigned-long numbers to and from ASCII
SYNOPSIS
#include <freeswan.h>
const char *atoul(const char * src, size_t srclen, int base, unsigned long * n);
size_t ultoa(unsigned long n, int base, char * dst, size_t dstlen);
DESCRIPTION
These functions are obsolete; see ipsec_ttoul(3) for their replacements.
Atoul converts an ASCII number into a binary unsigned long value. Ultoa does the reverse conversion, back to an ASCII version.
Numbers are specified in ASCII as decimal (e.g. 123), octal with a leading zero (e.g. 012, which has value 10), or hexadecimal with a
leading 0x (e.g. 0x1f, which has value 31) in either upper or lower case.
The srclen parameter of atoul specifies the length of the ASCII string pointed to by src; it is an error for there to be anything else
(e.g., a terminating NUL) within that length. As a convenience for cases where an entire NUL-terminated string is to be converted, a srclen
value of 0 is taken to mean strlen(src).
The base parameter of atoul can be 8, 10, or 16, in which case the number supplied is assumed to be of that form (and in the case of 16, to
lack any 0x prefix). It can also be 0, in which case the number is examined for a leading zero or a leading 0x to determine its base, or 13
(halfway between 10 and 16), which has the same effect as 0 except that a non-hexadecimal number is considered decimal regardless of any
leading zero.
The dstlen parameter of ultoa specifies the size of the dst parameter; under no circumstances are more than dstlen bytes written to dst. A
result which will not fit is truncated. Dstlen can be zero, in which case dst need not be valid and no result is written, but the return
value is unaffected; in all other cases, the (possibly truncated) result is NUL-terminated.
The base parameter of ultoa must be 8, 10, or 16.
Atoul returns NULL for success and a pointer to a string-literal error message for failure; see DIAGNOSTICS. Ultoa returns the size of
buffer which would be needed to accommodate the full conversion result, including terminating NUL; it is the caller's responsibility to
check this against the size of the provided buffer to determine whether truncation has occurred.
SEE ALSO
atol(3), strtoul(3)
DIAGNOSTICS
Fatal errors in atoul are: empty input; unknown base; non-digit character found; number too large for an unsigned long.
HISTORY
Written for the FreeS/WAN project by Henry Spencer.
BUGS
There is no provision for reporting an invalid base parameter given to ultoa.
The restriction of error reports to literal strings (so that callers don't need to worry about freeing them or copying them) does limit the
precision of error reporting.
The error-reporting convention lends itself to slightly obscure code, because many readers will not think of NULL as signifying success. A
good way to make it clearer is to write something like:
const char *error;
error = atoul( /* ... */ );
if (error != NULL) {
/* something went wrong */
11 June 2001 11/14/2008 IPSEC_ATOUL(3)