Hi,
There are a couple of things that I'm struggling with
unsuccessfully. :-( One of them is figuring out how
to get daemons to start up when the server starts, or
restarts, without having to start them manually. It
may be clearly defined in the handbook, but I am inept
enough to not see it.
Hi,
I've configured SAMBA as well as I could, but am still
missing how to get this all set up. Could someone send
their config file and drive configuration settings, or
whatever? Or just contact me (with a *lot* of
patience).
Thanks,
Micke
__
Do you Yahoo!?
Right! Ok, it's definitely not inetd that I need. I'm
thinking primarily of starting apache and a dynamic ip
updater automatically at startup.
Micke
--- fbsd_user [EMAIL PROTECTED] wrote:
Maybe you just don't understand what you are seeing.
Inetd is the
Super server. Every thing you
As a stop gap, I'd even be glad for info on seting up
ftp'ing with the windows machines on my LAN. Right now
I am ftp'ing to and from my ISP webspace.
Thanks,
Micke
I've configured SAMBA as well as I could, but am
still
missing how to get this all set up. Could someone
send
their config
If there is something that is done automatically, I
swear my karma is that it won't be done! I did do a
port apache install. And right, I don't remember that
being asked. I'm assuming there's an easier way to get
this set up besides redoing the install.
Examples of this script(working :-))?
Subhro
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Micke P
Sent: Monday, January 05, 2004 12:05 AM
To: [EMAIL PROTECTED]
Subject: starting daemons at server start
Hi,
There are a couple of things that I'm struggling
with
unsuccessfully
Woohoo! I changed the permissions on my apache shell
file and presto- apache now starts on rebooting!
Thanks very very much all of you for your very good
help. That's one less thing to be frazzled about.
Micke
--- Marty Landman [EMAIL PROTECTED] wrote:
At 02:21 PM 1/4/2004, Micke P wrote
thinking it's the
ISP, since I don't really understand how requests
could / or could not go from the dynamic IP to the
ISP-assigned LAN IP without their router or whatever.
Micke
--- Viktor Lazlo [EMAIL PROTECTED] wrote:
On Thu, 23 Oct 2003, Micke P wrote:
Hi,
Well, it's
, Micke P wrote:
Do you know what an ISP, earthlink, in this case,
might do to keep you from serving pages? I'm using
another port from 80, because I just get the ISP
modem
status page when using the dynamic IP with the
normal
80 port.
I doubt that would be the case, it is much more
Hi,
I'm having all kinds of trouble trying to get things
set up to see my website on the Internet. I know
people like to claim to be newbies, but I actually am.
:-)
My machine (ethernet card) IP is 192.168.254.25 and
I'm serving on port 8080. I can bring up the site no
problem on my LAN-
Hi Viktor,
See comments below.
--- Viktor Lazlo [EMAIL PROTECTED] wrote:
On Tue, 21 Oct 2003, Micke P wrote:
Hi,
I'm having all kinds of trouble trying to get
things
set up to see my website on the Internet. I know
people like to claim to be newbies, but I
--- Paul Everlund [EMAIL PROTECTED] wrote:
Micke P wrote:
My machine (ethernet card) IP is 192.168.254.25
and
I'm serving on port 8080. I can bring up the site
no
problem on my LAN- http://192.168.254.25:8080/,
but
not outside.
My ISP is earthlink and it's a dynamic IP account
--- [EMAIL PROTECTED] wrote:
I opened the port on my (hardware) router box, not
the
FreeBSD firewall. Internet - ISP - Modem -
Router
- FreeBSD box. Hopefully that's all I need to do
to
forward the port 8080 packets. Do I need to
configure
the FreeBSD firewall settings as well to
13 matches
Mail list logo
