Comments/Experience with DJBernstein's tools? supervise, djdns, dnscache
Does anyone have experience with D J Bernstein's tools, such as "daemontools", supervise, djdns, and/or dnscache? If so, can you tell me about reliability, if they are really worth replacing their counterparts (supervise <=> inittab; djdns/dnscache <=> bind ) and why?
I must write a script to change all C++ like comments:
// this is a comment
to this one
/* this is a comment */
How to do it by sed? With file:
#include <cstdio>
using namespace std; //one
// two
int main() {
printf("Example"); // three
}//four
the result should be: (2 Replies)
setup
192.168.1.0(windows)---------ROUTER---------192.168.0.0(linux)---->internet
djb tinydns/dnscache runs on linuxbox with 2 eth's with 2 IP's
tinydns = 192.168.0.237 on eth0
dnscache = 192.168.0.226 on eth0:0
when i put on the windows dns 192.168.0.237, i can nsloopup all the local... (0 Replies)
I know this is off subject, but I have been having fits with a Quantum M1500 library with DTL8000 drives, and figured that some of you have had some experience with them.
Thanks,
Chuck (1 Reply)
Hi everybody,
I'm kinda fed up with all the theoritical part of programming. I wonder if there is any online project or something where i can participate to practice my skills? Any other suggestions how to build up practical side of Unix C programming?
Thank you all. (1 Reply)
I'm kinda fed up with all the theoretical side of the programming. now i'd love to participate in some project dealing with C network programming under Unix. My question is: is there any online programs or projects where i can really participate? Any other suggestions how to build up practical... (1 Reply)
readproctitle(8) System Manager's Manual readproctitle(8)NAME
readproctitle - maintains an automatically rotated log in memory for inspection by ps(1).
readproctitle is available in daemontools 0.75 and above.
SYNOPSIS
readproctitle L D
DESCRIPTION
L consists of any number of arguments. D is one argument consisting of at least five dots.
readproctitle reads data into the end of D, shifting D to the left to make room. This means that the most recent data is visible to
process-listing tools such as ps(1). readproctitle always leaves three dots at the left of D.
For example, if
readproctitle io errors: ....................
reads the data
fatal error xyz
warning abc
then its command-line arguments change to
readproctitle io errors: ... xyz!warning abc!
with a newline character in place of each !. Process-listing tools typically show the newline character as ? or
.
readproctitle exits when it reaches the end of input.
Beware that most implementations of ps(1) have small argument-length limits. These limits apply to the total length of readproctitle L D.
I have not seen a system with a limit below 512 bytes.
SEE ALSO supervise(8), svc(8), svok(8), svstat(8), svscanboot(8), svscan(8), fghack(8), pgrphack(8), multilog(8), tai64n(8), tai64nlocal(8), setu-
idgid(8), envuidgid(8), envdir(8), softlimit(8), setlock(8), ps(1)
http://cr.yp.to/daemontools.html
http://cr.yp.to/slashcommand.html
readproctitle(8)