How do you control the shutdown?
If it is a simple logical signal, i.e. either high or low voltage, perhaps
the easiest way would be a hardware solution.
It could be as simple as a diode, a large capasitor and a resistor.
Your local electronic supplyer could probably build a delay
Hi Folks,
I need to execute a script (which tells the UPS to turn off) *after* the
system has come to a safe halt from shutdown -h. I can't place the commands
in /etc/rc.shutdown because this is too early in the shutdown sequence.
Unfortunately, the UPS in question (APC Back-UPS 650) is not a
On 19 May 2000, Doug White wrote:
On Fri, 19 May 2000, Cillian Sharkey wrote:
I need to execute a script (which tells the UPS to turn off) *after* the
system has come to a safe halt from shutdown -h. I can't place the commands
in /etc/rc.shutdown because this is too early in the shutdown
Looks like a firewall to me. Either a firewall in a router
sitting between the hosts, or an ipfw setup sitting on one or the
other host.
I set up the NFS server in question ages ago. I haven't looked at the
problem, but... The server does use ipfw. The broken client is on
Hi folks,
I've been trying to accomplish the simple task of mounting filesystems
from a central server 'hostA' onto a new client 'hostB'. the new client
has a basic 3.3 'bin' distrib installed on it and I am trying to mount
/usr/src /usr/obj from hostA so that I can upgrade it.
the problem is
Ben Rosengart wrote:
How would people feel about excluding procfs from the output of df?
df -t noprocfs
and voila no procfs in the output !
Cillian
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Ben Rosengart wrote:
How would people feel about excluding procfs from the output of df?
df -t noprocfs
and voila no procfs in the output !
Cillian
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message
Ok, I'm going to start doing a bit of work on this
so as to enable the periodic output to be customised
I'll post my changes later for ppl that maybe interested
(these changes will still be useful for myself anyway)
I'll see if I can put all your suggestions in, thanks
for the feedback.
Ok, I'm going to start doing a bit of work on this
so as to enable the periodic output to be customised
I'll post my changes later for ppl that maybe interested
(these changes will still be useful for myself anyway)
I'll see if I can put all your suggestions in, thanks
for the feedback.
Cillian
Hi,
Currently, the reports that are generated and emailed to root are
fine in what they do. however, a lot of the time there is actaully
nothing of interest in these reports if nothing has gone wrong
on the system etc. Basically I only want to know about the changes
that have happened. This
Hi,
Currently, the reports that are generated and emailed to root are
fine in what they do. however, a lot of the time there is actaully
nothing of interest in these reports if nothing has gone wrong
on the system etc. Basically I only want to know about the changes
that have happened. This would
Ideas / Comments / Suggestions ?
^ ^^^
Well ?
Diffs ?
I haven't actually done any work on this (yet)
but I might see what I can hack together..
;)
Cillian
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe
Make sure they always generate some output so that a message
does get mailed. On more than once occasion I noticed that one
of my boxes keeled over or the network broke when I didn't
get my expected daily output from that machine.
My proposal would only *cut down* on all the white space,
This may not be a good idea. I often check daily reports to see if
a disk has suddenly filled or had been gradually filling over a
long period of time - you wouldn't be able to get this info if you
print stuff selectively.
in the case of df, one could set whether you want full df status OR
My name is estee, i am new in Freebsd. Can anyone help me to solve this
problem? I want to add a new domain name in domain name server(freebsd),
how i do it? Thanks in advance, please help, this is urgent...
Well no doubt the FreeBSD box is running BIND...so the configuration
file for
Hi,
change to /sys/net/if.c which will print out
"xxN: promiscuous mode disabled" msg to match its
equiv. "xxN: promiscuous mode enabled" msg
works on all my interfaces even if tcpdump is run
multiple times etc. However it does not print out
the disabled msg for tun0 interface for some
+ log(LOG_INFO, "%s%d: promiscuous mode disabled\n",
+ ifp-if_name, ifp-if_unit);
You're the second person other than me to request this. :-)
Yes, i've seen it suggested before alright..
So are there any _objections_ to having the kernel match
I think, the "disabled" messages output should be put under `if (verbose)'.
Maybe..there was a lot of talk on another mailing list (-current I think?)
about boot messages, level of verbosity etc. etc. so perhaps
we should wait until this has been decided.. ?
- Cillian
To Unsubscribe: send
Another question that comes in to this is - how good a tool is nmap
for evaluating the predictability of the sequence numbers we generate?
Ideally, I would like to do some improvements to our sequence number
generation.
Thoughts?
What is OpenBSD like in this regard ?
AFAIR it has
My name is estee, i am new in Freebsd. Can anyone help me to solve
this
problem? I want to add a new domain name in domain name server(freebsd),
how i do it? Thanks in advance, please help, this is urgent...
Well no doubt the FreeBSD box is running BIND...so the configuration
file
Hi,
change to /sys/net/if.c which will print out
xxN: promiscuous mode disabled msg to match its
equiv. xxN: promiscuous mode enabled msg
works on all my interfaces even if tcpdump is run
multiple times etc. However it does not print out
the disabled msg for tun0 interface for some mysterious
+ log(LOG_INFO, %s%d: promiscuous mode disabled\n,
+ ifp-if_name, ifp-if_unit);
You're the second person other than me to request this. :-)
Yes, i've seen it suggested before alright..
So are there any _objections_ to having the kernel match promiscuous
I think, the disabled messages output should be put under `if (verbose)'.
Maybe..there was a lot of talk on another mailing list (-current I think?)
about boot messages, level of verbosity etc. etc. so perhaps
we should wait until this has been decided.. ?
- Cillian
To Unsubscribe: send mail
Sheldon Hearn wrote:
On Fri, 20 Aug 1999 15:55:45 +0100, Cillian Sharkey wrote:
Maybe..there was a lot of talk on another mailing list (-current I think?)
about boot messages, level of verbosity etc. etc. so perhaps
we should wait until this has been decided.. ?
This has nothing
Another question that comes in to this is - how good a tool is nmap
for evaluating the predictability of the sequence numbers we generate?
Ideally, I would like to do some improvements to our sequence number
generation.
Thoughts?
What is OpenBSD like in this regard ?
AFAIR it has various
Hi,
I just setup my system so that "Joe" user can mount
/dev/fd0 on a mountpoint "Joe" owns..grand no problem..
..BUT it only works when the f/s code for that f/s type is
available (ie. compiled into the kernel or has been previously
loaded as a module)
however if it's not compiled into the
Hi,
I just setup my system so that Joe user can mount
/dev/fd0 on a mountpoint Joe owns..grand no problem..
..BUT it only works when the f/s code for that f/s type is
available (ie. compiled into the kernel or has been previously
loaded as a module)
however if it's not compiled into the kernel,
if (--ifp-if_pcount 0)
return (0);
ifp-if_flags = ~IFF_PROMISC;
---log(LOG_INFO, "%s%d: promiscuous mode disabled\n",
---ifp-if_name, ifp-if_unit);
Shouldn't this be:
if (ipf-if_flags
But what happens if you write a program which does whatever ioctl is
required to unpromiscify an interface and run it on an unpromiscuous
interface, does it print a message to syslog even though promiscuous
mode was never enabled in the first place?
Like I said, I seem to get the
is the system still booting off the IDE disk (if present) ?
Yes. But not from the SCSI
You can try setting the BIOS to boot from the SCSI disk which should
do the trick..unless you have a crappy BIOS that doesn't let you do
that.. :(
With fdisk I set the partition as bootable on the SCSI
if (--ifp-if_pcount 0)
return (0);
ifp-if_flags = ~IFF_PROMISC;
---log(LOG_INFO, %s%d: promiscuous mode disabled\n,
---ifp-if_name, ifp-if_unit);
Shouldn't this be:
if (ipf-if_flags
But what happens if you write a program which does whatever ioctl is
required to unpromiscify an interface and run it on an unpromiscuous
interface, does it print a message to syslog even though promiscuous
mode was never enabled in the first place?
Like I said, I seem to get the
but in the boot up, the message, "changing root device to wd0s1" keeps appearing and
keeps
failing. in my /etc/fstab i have the following entry:
/dev/sd0s1a/ufs rw11
does anyone have any ideas.
the sd0 is probed and attached successfully during startup, but the
when a network interface is put into promiscuous mode, a kernel
message is logged ie. "ep0: promiscuous mode enabled" are there plans
to log the reverse of this message ie. "ep0: promiscuous mode
disabled"..I think this was suggested before in the mailing-lists but
did anything
but in the boot up, the message, changing root device to wd0s1 keeps
appearing and keeps
failing. in my /etc/fstab i have the following entry:
/dev/sd0s1a/ufs rw11
does anyone have any ideas.
the sd0 is probed and attached successfully during startup, but the
when a network interface is put into promiscuous mode, a kernel
message is logged ie. ep0: promiscuous mode enabled are there plans
to log the reverse of this message ie. ep0: promiscuous mode
disabled..I think this was suggested before in the mailing-lists but
did anything come of
Hi,
On my system here, wd0: windoze wd1: FreeBSD wd2: blankdisk
When I boot up under a 3.2-STABLE kernel (recently updated),
wdc1 is "not found"
However when I boot up under a 3.1-RELEASE "generic" kernel
it sees the drive (wd2) and controller (wdc1) ok. (And yes I
do have an entry for
Yes, i'm also facing the same problem in 3.2 stable (wdc1 not found at 0x170).
When i put a CD-ROM (ATAPI, secondary slave) sometimes the controller comes up
;) I tried my own kernel (by changing the IDE delay), it didn't work.
-biju
Normally for my own kernel, I set the IDE delay very low
I am trying to install both 2.2.8 and 3.2 on a single 17Gb HDD, but
am not having much luck. I have tried several approaches, in particular
creating four partitions, the first two for the respective root slices,
the third for swap, and the fourth for the remaining slices. If I create
the first
I tried with delay 12000, 6000, 8000 (I admit that i really don't know how this
delay helps) but no use... only putting a CD in the drive while booting helps.
-biju
I just set IDE_DELAY=4000 in my 3.2-STABLE kernel, and now it sees all disks
on both controllers. I think the problem was that
This works, but has the restriction that I have to enter a command line
at the boot prompt to boot one of the two. I would much prefer
partitions, as I can use a boot selector instead, and also change the
default as appropriate.
If you do have the installations in two seperate slices on the
If you do have the installations in two seperate slices on the one disk,
you should be able to use a boot selector to boot which ever slice you
want.
Boot selector programs like os-bs work with partitions, not disk slices.
That's why I wanted separate partitions. At the moment I have
Hi,
On my system here, wd0: windoze wd1: FreeBSD wd2: blankdisk
When I boot up under a 3.2-STABLE kernel (recently updated),
wdc1 is not found
However when I boot up under a 3.1-RELEASE generic kernel
it sees the drive (wd2) and controller (wdc1) ok. (And yes I
do have an entry for wdc1,wd2,wd3
Yes, i'm also facing the same problem in 3.2 stable (wdc1 not found at 0x170).
When i put a CD-ROM (ATAPI, secondary slave) sometimes the controller comes up
;) I tried my own kernel (by changing the IDE delay), it didn't work.
-biju
Normally for my own kernel, I set the IDE delay very low
I am trying to install both 2.2.8 and 3.2 on a single 17Gb HDD, but
am not having much luck. I have tried several approaches, in particular
creating four partitions, the first two for the respective root slices,
the third for swap, and the fourth for the remaining slices. If I create
the first two
I tried with delay 12000, 6000, 8000 (I admit that i really don't know how
this
delay helps) but no use... only putting a CD in the drive while booting helps.
-biju
I just set IDE_DELAY=4000 in my 3.2-STABLE kernel, and now it sees all disks
on both controllers. I think the problem was that
This works, but has the restriction that I have to enter a command line
at the boot prompt to boot one of the two. I would much prefer
partitions, as I can use a boot selector instead, and also change the
default as appropriate.
If you do have the installations in two seperate slices on the
If you do have the installations in two seperate slices on the one disk,
you should be able to use a boot selector to boot which ever slice you
want.
Boot selector programs like os-bs work with partitions, not disk slices.
That's why I wanted separate partitions. At the moment I have
48 matches
Mail list logo
