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)
svscan(8) System Manager's Manual svscan(8)NAME
svscan - starts and monitors a collection of services
SYNOPSIS
svscan [ directory ]
DESCRIPTION
svscan starts one supervise(8) process for each subdirectory of the current directory, up to a limit of 1000 subdirectories. svscan skips
subdirectory names starting with dots. supervise(8) must be in svscan's path.
svscan optionally starts a pair of supervise(8) processes, one for a subdirectory s, one for s/log, with a pipe between them. It does this
if the name s is at most 255 bytes long and s/log exists. (In versions 0.70 and below, it does this if s is sticky.) svscan needs two free
descriptors for each pipe.
Every five seconds, svscan checks for subdirectories again. If it sees a new subdirectory, it starts a new supervise(8) process. If it sees
an old subdirectory where a supervise(8) process has exited, it restarts the supervise(8) process. In the log case it reuses the same pipe
so that no data is lost.
svscan is designed to run forever. If it has trouble creating a pipe or running supervise(8), it prints a message to stderr; it will try
again five seconds later.
If svscan is given a command-line argument directory, it switches to that directory when it starts.
SEE ALSO supervise(8), svc(8), svok(8), svstat(8), svscanboot(8), readproctitle(8), fghack(8), pgrphack(8), multilog(8), tai64n(8), tai64nlocal(8),
setuidgid(8), envuidgid(8), envdir(8), softlimit(8), setlock(8)
http://cr.yp.to/daemontools.html
svscan(8)