\_
\_ [...] In other words do not buy in that any one company
\_ can give the total answer. Study, study, and study some more before
\_ you make a decision. Remember making the wrong decision at this
\_ point will come back to haunt you latter.
In my days in highschool woodshop, this was refered to "measure twice,
cut once". The 1:1 ratio was always dangerous...sometimes you were
ok, sometimes you'd cut twice and it'd still be too short.
As for Bugzilla, it is without a doubt the very best bug tracking
system I have ever used. I suppose I should mention that it is also
the *only* bug system that was more complex than commented warnings in
the code. :-)
David
From Don Harrop <
don@nis4u.com> Fri Dec 1 00:47:11 2000
From: Don Harrop <
don@nis4u.com> (Don Harrop)
Date: Thu, 30 Nov 2000 17:47:11 -0700 (MST)
Subject: init.d startup scripts.
Message-ID: <
Pine.LNX.4.21.0011301723270.17682-100000@tech1.nis4u.com>
Hey pluggers.
I've written an HPUX init.d startup script to start sshd at bootup.
The problem is that no matter what I do the daemon is killed off after
init.d is over. I know that it starts because I've encorporated a ps
command to output to a file in my script and it is a process running.
After I log in though and do an lsof -i :22 or a ps to find my sshdaemon
it's not there. I've tried starting it with an & for a background process
and that doesn't work. I've also tried su'ing to root and executing sshd
but I get an error message saying I don't have execute permissions. sshd
is chmod'ed 755 so it should be able to execute. I need a bone here
guys.. :-)
(text/plain)