02-06-2019
I found the issue, the second code fragment has a logical mistake.
8 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
When discussing inodes and data blocks, I know Solaris creates these data blocks with a total size of 8192b, divided into eight 1024b "fragments." It stores data in "contiguous" fragments and solaris doesn't allow a file to use portions of two different fragments. If the file size permits, then the... (4 Replies)
Discussion started by: manderson19
4 Replies
2. Post Here to Contact Site Administrators and Moderators
Hi guys!
I was wondering what the outcome was of your survey of a few months ago? One of the questions was if people were willing to pay for additional services like an own account, like username@unix.com with mail box, etc.
Sorry if I missed the results if you had already posted them.
Ivo (1 Reply)
Discussion started by: Ivo
1 Replies
3. Solaris
For some reason ipfilter is blocking inbound fragmented ip packets (the packets are larger than the interface's MTU) that are encapsulating UDP segments. The connection works, so I know ipfilter is letting some traffic through, it is just a lot slower than it should be.
Rules that allow the... (3 Replies)
Discussion started by: ilikecows
3 Replies
4. IP Networking
Upon replacing my linux router/server with a Solaris one I've noticed very poor network performance. The server itself has no issues connecting to the net, but clients using the server as a router are getting a lot of IP fragments as indicated from some packet sniffing I conducted.
Here was my... (3 Replies)
Discussion started by: vectox
3 Replies
5. Shell Programming and Scripting
Hello ,
When using vim, can ctag and cscope support recording search results and displaying the history results ? Once I jump to one tag, I can use :tnext to jump to next tag, but how can I display the preview search result? (0 Replies)
Discussion started by: 915086731
0 Replies
6. Shell Programming and Scripting
# echo '1 2 3 ' | awk -F' ' '{print NF}'
3
# echo '1:2:3:' | awk -F':' '{print NF}'
4 (1 Reply)
Discussion started by: lazycat79
1 Replies
7. Shell Programming and Scripting
I have a .xml file that looks something like this :
<measInfo>
.........
string1
.........
</measInfo>
<measInfo>
......
string2
........
</measInfo>
I want to extract only the 'chunk of file' from '<measInfo>' to '</measInfo>' containing string1 (or a certain string that I... (13 Replies)
Discussion started by: black_fender
13 Replies
8. Shell Programming and Scripting
Good morning all,
This is the file name in question OD_Orders_2019-02-19.csv
I am trying to create a bash script to read into files with yesterdays date on the file name while retaining the rest of the files name. I would like for $y to equal, the name of the file with a formula output with... (2 Replies)
Discussion started by: Ibrahim A
2 Replies
LEARN ABOUT DEBIAN
gd_fragmentname
gd_fragmentname(3) GETDATA gd_fragmentname(3)
NAME
gd_fragmentname -- retrieve a dirfile format specification fragment name
SYNOPSIS
#include <getdata.h>
const char* gd_fragmentname(const DIRFILE *dirfile, int index);
DESCRIPTION
The gd_fragmentname() function queries a dirfile(5) database specified by dirfile and returns the filename of the format specification
fragment indexed by the non-negative index.
The dirfile argument must point to a valid DIRFILE object previously created by a call to gd_open(3).
The fragment with index equal to zero is always the primary fragment for the database (the file called format in the root dirfile directo-
ry). The largest valid value of index is one less than the total number of fragments, which may be obtained from a call to gd_nfrag-
ments(3).
RETURN VALUE
Upon successful completion, gd_fragmentname() returns a pointer to a read-only character string containing the file name of the specified
fragment. On error, gd_fragmentname() returns NULL and sets the dirfile error a non-zero error value. Possible error values are:
GD_E_BAD_DIRFILE
The supplied dirfile was invalid.
GD_E_BAD_INDEX
The supplied index was out of range.
The dirfile error may be retrieved by calling gd_error(3). A descriptive error string for the last error encountered can be obtained from
a call to gd_error_string(3).
SEE ALSO
dirfile(5), gd_error(3), gd_error_string(3), gd_include(3), gd_nfragments(3), gd_open(3), gd_parent_fragment(3)
Version 0.7.0 21 July 2010 gd_fragmentname(3)