06-23-2010
thanks jim and jasondj for the replies
yes by calling conventions I mean _CDECL and _STDCALL.
when should a user have to bother about it?
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
I have 2 scripts, one is the .profile and the other is a SID selector for Oracle Databases.
But when I call one from the other, even though it seems to have worked, it doesn't.
Can anyone help??
******************* .profile**********************
#!/bin/ksh
.... (5 Replies)
Discussion started by: dnkansah
5 Replies
2. Shell Programming and Scripting
OK, I'm very new to shell scripting, and I'm trying to write a (very) simple wrapper for sendmail that outputs all the arguments as well as the file that called sendmail to an output file which can later be looked over.
Is it possible to get a file's name and path that called a script? (0 Replies)
Discussion started by: ghstber
0 Replies
3. UNIX for Advanced & Expert Users
Hello,
I'm wondering what is the naming conventions for *.so shared libraries in linux. For example, a library in /lib, say libcrypt-2.7.so has a symbolic link called libcrypt.so.1 pointing to it, yet libncursesw.so.5.6 has a symbolic link called libncursesw.so.5 pointing to it. What is the... (2 Replies)
Discussion started by: neked
2 Replies
4. Solaris
These are findings by me with my little experience with Solaris 10. Please correct me if wrong..
In x86 systems with ide hard disk:
c= controller
d=disk
s=slice
1.Here controller c0 means the primary ide controller ide0.
controller c1 means the secondary ide controller ide1.
... (5 Replies)
Discussion started by: saagar
5 Replies
5. UNIX for Dummies Questions & Answers
I would like to use an automated checker for adherence to CSS coding conventions. I have browsed the web, but no tool I came across checks for coding conventions, only syntax. Here is a general list of requirements:
- Style definitions should be separated by one blank line
- Indentation is 2... (0 Replies)
Discussion started by: figaro
0 Replies
6. UNIX for Dummies Questions & Answers
i was viewing the gawk's man file,checked the man faqs,didnt find anything about the char "e" meaning
.TP
.B \e`
matches the empty string at the beginning of a buffer (string).
.TP
.B \e'
matches the empty string at the end of a buffer.after convention,it should looks like thie
\` ... (2 Replies)
Discussion started by: b33713
2 Replies
7. UNIX for Dummies Questions & Answers
is there a typographic convention that is followed in the man pages.
where could a description be found.
at this time i am in man stty and the author uses upper case in some places.
and my brain is just burning to a fizzle while studying a book on bash and trying to stay in scope of the... (1 Reply)
Discussion started by: cowLips
1 Replies
8. Shell Programming and Scripting
Hi. I have been running some scripts ok with no extension on the name, and they work fine. What difference does it make if I call them whatever.sh? And I have some scripts starting #!/bin/bash - which debian recognises as shell scritps, even without the .sh ending - and some which don't. I'm sure... (8 Replies)
Discussion started by: triplemaya
8 Replies
9. Cybersecurity
Hey guys, not sure should I post it here or in 'What is on Your Mind?'
I'm discussing usage of DSL (domain specific language) in security tools with my colleagues. We haven't been able to reach an agreement over naming conventions.
There are many tools using DSL: splunk, sumologic,... (2 Replies)
Discussion started by: Tobby P
2 Replies
10. Linux
I'm slowly hacking away at a zsh script that shows some promise as a command line tool. I want to learn more about the conventions regarding command line tool development in Unix (and/or macOS), but don't really know where to look for this information.
What is the correct way, or convention, to... (2 Replies)
Discussion started by: MonilGomes
2 Replies
LEARN ABOUT DEBIAN
in.tftpd
TFTPD(8) BSD System Manager's Manual TFTPD(8)
NAME
tftpd -- DARPA Trivial File Transfer Protocol server
SYNOPSIS
tftpd [-n] [-s] [directory ...]
DESCRIPTION
Tftpd is a server which supports the DARPA Trivial File Transfer Protocol. The TFTP server operates at the port indicated in the 'tftp' ser-
vice description; see services(5). The server is normally started by inetd(8).
The use of tftp(1) does not require an account or password on the remote system. Due to the lack of authentication information, tftpd will
allow only publicly readable files to be accessed. Files may be written only if they already exist and are publicly writable. Note that
this extends the concept of ``public'' to include all users on all hosts that can be reached through the network; this may not be appropriate
on all systems, and its implications should be considered before enabling tftp service. The server should have the user ID with the lowest
possible privilege.
Access to files may be controlled by invoking tftpd with a list of directories by including pathnames as server program arguments in
/etc/inetd.conf. In this case access is restricted to files whose names are prefixed by the one of the given directories. If no directories
are supplied the default is /tftpboot. To give out access to the whole filesystem, should this be desired for some reason, supply / as an
argument.
Unfortunately, on multi-homed systems, it is impossible for tftpd to determine the address on which a packet was received. As a result, tftpd
uses two different mechanisms to guess the best source address to use for replies. If the socket that inetd(8) passed to tftpd is bound to a
particular address, tftpd uses that address for replies. Otherwise, tftpd uses ``UDP connect'' to let the kernel choose the reply address
based on the destination of the replies and the routing tables. This means that most setups will work transparently, while in cases where the
reply address must be fixed, the virtual hosting feature of inetd(8) can be used to ensure that replies go out from the correct address.
These considerations are important, because most tftp clients will reject reply packets that appear to come from an unexpected address.
The options are:
-n Suppresses negative acknowledgement of requests for nonexistent relative filenames.
-s All absolute filenames are treated as if they were preceded by the first directory argument, or /tftpboot if there is none.
SEE ALSO
tftp(1), inetd(8)
HISTORY
The tftpd command appeared in 4.2BSD.
Linux NetKit (0.17) July 29, 2000 Linux NetKit (0.17)