03-30-2006
Just noticed. I CAN run a dhcp-client as root to make re-establish the connection. And it's 1800 seconds until it dies (half an hour?) . How can I stop this annoying behaviour?
8 More Discussions You Might Find Interesting
1. IP Networking
hie guys
I am running fedora 6 on remote machines which are connecting to my server. The remote machines connect through one machine (more like my router) to the server. The problem i am having is that the remote machines are suppose to be reporting in real time mode to the server. Most of these... (2 Replies)
Discussion started by: no3more
2 Replies
2. Linux
I was wondering if it is possible to setup SFTP to go through the internet proxy while connecting to an internet location.
Problem: Client system is behind internet proxy. SFTP to any internet location fails as there is no documented way to configure SFTP to connect to internet locations through... (4 Replies)
Discussion started by: toobrown1
4 Replies
3. Programming
Hi,
(First post, please be gental!)
I have a java app that I am running on unix (centos)
But it keeps dying randomly. The times seem random from anything between 3 hours and 3 days.
I have a cronjob running to restart it when ever it dies but I would rather this happened less often.
... (2 Replies)
Discussion started by: sm9ai
2 Replies
4. Shell Programming and Scripting
I have an Ubuntu machine that I'd like to update automatically. I've written an expect script to run the aptitude package manager and update my packages. Essentially it does:
aptitude update && aptitude upgrade while answering "yes" at the appropriate time.
It works quite nicely when run... (4 Replies)
Discussion started by: CluelessPerson
4 Replies
5. Shell Programming and Scripting
Hi folks,
Friendly router geek wanting to be a programmer here...
So I worked with another guy here and came up with this to capture Unix admin data:
#!/bin/ksh
#
#
# Set Default Paths
#
PATH=/usr/apps/client/bin:$PATH; export PATH... (4 Replies)
Discussion started by: Marc G
4 Replies
6. Red Hat
Hello All,
SNMPD dying after 2 mins once it started. Here is the configuration
Oct 12 04:43:00 localhost systemd: Starting Simple Network Management Protocol (SNMP) Daemon....
Oct 12 04:43:00 localhost snmpd: dlopen failed: /usr/lib64/libcmaX64.so: cannot open shared object file: No such... (1 Reply)
Discussion started by: shekar777
1 Replies
7. Debian
Hello,
I need to upgrade my Debian system 7.8 to 8.5 but by default via apt-get It moves to 8.6 version(latest stable version). I'm new to Debian so didn't figure out the solution.
I've checked few suggestions over internet like editing apt source list file using snapshot archive.
Please... (2 Replies)
Discussion started by: Mannu2525
2 Replies
8. What is on Your Mind?
Source
a quick google search making clear that this isn't really new, and if we look at our bsd Forum we see that its the only operation systems forum with the last comment dated to June last year, whereas all the others have more recent comments.
One comment dated to 2014 is exactly what I... (10 Replies)
Discussion started by: dodona
10 Replies
LEARN ABOUT OPENSOLARIS
mdmonitord
mdmonitord(1M) System Administration Commands mdmonitord(1M)
NAME
mdmonitord - daemon to monitor metadevices
SYNOPSIS
/usr/sbin/mdmonitord [-t time_interval]
DESCRIPTION
The mdmonitord utility is part of Solaris Volume Manager. It monitors and checks RAID1 (mirrors), RAID5 and hot spares.
There are two methods for checking:
o At fixed time intervals.
o When a RAID-1 (mirror), RAID-5, or hot spare fails. A failure generates an error event which triggers a check of these metade-
vices.
OPTIONS
The following options are supported:
-t Time interval in seconds. The default value is 0, which causes probes to occur only upon an error. If you want to run mdmonitord at
a regular interval, a value of 1800 (seconds, every half hour) is recommended as a starting point.
EXIT STATUS
The following exit values are returned:
0 Successful completion.
>0 An error occurred.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWmdu |
+-----------------------------+-----------------------------+
SEE ALSO
svcs(1), metaclear(1M), metadb(1M), metadetach(1M), metahs(1M), metainit(1M), metaoffline(1M), metaonline(1M), metaparam(1M), metare-
cover(1M), metarename(1M), metareplace(1M), metaroot(1M), metaset(1M), metassist(1M), metastat(1M), metasync(1M), metattach(1M),
svcadm(1M), md.tab(4), md.cf(4), mddb.cf(4), md.tab(4), attributes(5), smf(5), md(7D)
NOTES
Since frequent probes can affect performance, it is recommended that the intervals between probes be limited.
The mdmonitord service is managed by the service management facility, smf(5), under the service identifier:
svc:/system/mdmonitor
Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). The ser-
vice's status can be queried using the svcs(1) command.
SunOS 5.11 25 Jul 2004 mdmonitord(1M)