One more step towards OT, and yet on the spot. Now it is on 'beauty'.
At shutdown, we get always
"stopping package daemons:/etc/rc[260]: /etc/rc.d/: cannot execute -
Is a directory"
Is there anything wrong, still, with our configuration?
Uwe
On Wed, Mar 14, 2012 at 10:22 PM, Uwe Dippel wrote:
> I had read those. And yet, I don't understand that line. It doesn't
> look like it should be written into rc.conf / rc.conf.local, does it?
> Correct me if I'm wrong. It looks like a shell variable that has
> &#
On Wed, Mar 14, 2012 at 8:35 PM, Rodolfo Gouveia wrote:
>> And slightly OT: I have stared at the
>> pkg_scripts="${pkg_scripts} postfix" in the Upgrade Guide, and still
>> don't grasp what this is supposed to do, and where; since I am running
>> postscript.
>
> http://www.openbsd.org/faq/faq10.ht
On Wed, Mar 14, 2012 at 6:55 PM, Fred Crowson wrote:
> What does your logs say in /var/mysql/ ?
>
> hth
Yes, Fred, very much! - It is obvious that I failed - and still fail -
to understand the new startup system. Can anyone point me to a
complete overview to read up on it?
I don't get yet which
On Wed, Mar 14, 2012 at 7:27 PM, Norman Golisz wrote:
> However, did you change any values in php.ini from default?
no, not yet. I wasn't actually expecting everything to be up 100%, but
to be up, with the 50-default php-5.2.ini. Or, with the previous
php.ini in that place.
I also looked at the
I have this unfortunate occurrence on one of my production machines:
"Database Error: Unable to connect to the database:Could not connect to MySQL"
I studied the Upgrade Guide 4.9 to 5.0 intensely before and after, but
can't find what went wrong. I just did the upgrade, and made the links
as propos
On Fri, May 6, 2011 at 3:33 PM, Otto Moerbeek wrote:
> The original files didn't differ, but the install replaced Singapore
> to which /etc/localtime syms. So after resolving symlinks
> /etc/localtime did change.
>
> You copy in your postfix install wasn't changed.
Thanks, Otto, for the explanat
I did the upgrade 4.8->4.9 as lined out in
http://www.openbsd.org/faq/upgrade49.html
Now I get in the daily insecurity:
Checking special files and directories.
Output format is:
filename:
criteria (shouldbe, reallyis)
etc/nsd.conf:
gid (97, 0)
Did I miss anything? (
Just had a problem with softraid on a 4.6 box. No, I don't ask to solve
it, it needed urgent replacement, and so I did.
What I would like to ask for, is advice on best practices for softraid
under OpenBSD, to prevent similar things from happening again; getting
hints on how to set it up better,
Philip Guenther gmail.com> writes:
> You now have and now it
> seems the core discussion is just about whether (or where) an
> additional "rm -rf /usr/obj/*" should be added to help people that
> know enough to set up the source tree for building/patching by
> untaring src.tar.gz but don't know t
Philip Guenther gmail.com> writes:
> Please point to the part of the Upgrade Guide which talks about
> building from source, untarring the src tar file, or applying errata.
> I can't seem to find any such reference, but I'm sure it's in there
> somewhere, because you originally said that you did
Tony Abernethy servasoftware.com> writes:
> Might be better to read and comprehend ``man patch'' before assuming
> limitations on the scope of patch's reach.
It is always so nice to trample on the person lying on the ground, ain't it!
Where in 'man patch' is the underlying problem addressed? - o
Jacob Meuser sdf.lonestar.org> writes:
> oh good grief. you had a dirty /usr/obj.
>
> just look at the pfctl snippet of the log you posted. do you see pfctl
> being built? do you see pfctl being installed from /usr/obj?
Oh, yes. So the blame is on my side, I guess. Mea culpa maxima!
I didn't
On Fri, Jun 4, 2010 at 4:22 PM, Eric Faurot wrote:
> Don't you have old stuff lying around in /usr/obj that gets installed
> over your new binaries?
That's probably the critical question now. Though, sorry to say, there
is nowhere written that you have to rm -Rf it, when you
- upgrade
- patch
On Fri, Jun 4, 2010 at 4:32 PM, patrick keshishian wrote:
> Where did you get those tar-balls from? Those are most likely not 4.7 sources.
I gave the potential link and their md5 sums further up. Our link here
is sooo slooow; I *am* currently downloading the archives from
ftp://ftp.openbsd.org/p
On Fri, Jun 4, 2010 at 3:00 PM, Richard Toohey
wrote:
> I think we are getting closer, aren't we?
>
> So, NOTHING to do with the actual upgrade, is it?
No absolutely nothing. I withdraw the subject with regret. At least
the 'base47'-part thereof.
> Or the ports/packages.
I guess, not.
> It is
On Fri, Jun 4, 2010 at 2:41 PM, patrick keshishian wrote:
> you mean applying the errata47.html patches? If so, are you certain
> your source tree is tagged OPENBSD_4_7 and not anything else?
Do I understand you correctly? I am not building releases. I am
installing/downloading the sets; then I
On Fri, Jun 4, 2010 at 2:18 PM, Uwe Dippel wrote:
> 5. reboot after patching - old files and wrong timestamps - bummer, as
> Theo might say.
Sorry, guys, (too quick as too often), just cat-grep pfctl shows where
the old one comes in:
pfctl: pf already enabled
# ls -l # ls -l /etc/# ls -l
On Thu, Jun 3, 2010 at 7:18 PM, Richard Toohey
wrote:
> OK, I've tried it and cannot reproduce what you see. I've never done
> an upgrade from bsd.rd before, so wanted to give it a go.
>
> Obviously something different with your set-up, or where you got the files
> from, or factor X - but as oth
Damon McMahon gmail.com> writes:
> Probably no help, but I had similar happen to me upgrading 4.5->4.6 a
> few months ago. Similar problem with pftcl after a diligent upgrade,
> and like you I have been following the upgrade procedure diligently
> since 3.something. I checked the timestamp on pf
On Thu, Jun 3, 2010 at 3:20 PM, Tony Abernethy wrote:
> The error message(s) you are suppressing (or maybe didn't see)
>
> About the only way you can get some files but not all files
> from a tarball is some fatal error in the extraction of the
> tarball. Any such error tends to give an error mes
Theo de Raadt cvs.openbsd.org> writes:
> A chit-chat on a public mailing list isn't going to find this supposed
> bug. Why discuss it? Why not just keep prove it happened.
Yes, Theo. Though: How? This is what I tried to find out.
I showed the list if files. Do you assume I tinkered with it? W
Nick Holland holland-consulting.net> writes:
> > There is one more machine (amd64) that needs to be upgraded. Before I do
> > this, I rather solicit suggestions on how to log the upgrade process,
> > debug it, or otherwise.
>
> serial console.
> Log everything from the first chars out the seri
Now, with
$ diff md5sums_archive md5sums_install | grep ^">" | cut -d ' ' -f2
these are the files different on amd64, between what the archive
supplied, and what the installer left behind:
./usr/lib/libasn1.so.17.0
./usr/lib/libcom_err.so.17.0
./usr/lib/libcrypto.so.18.0
./usr/lib/libkafs.so.1
Getting closer ...
Extracted the archive being used for the upgrade to amd64 into my
user-directory and calculated all 7484 md5 for the files included in
base47, and redirected those into a file.
Then, I calculated all the md5 for the files *installed* in the upgraded
machine; the file names t
Joachim Schipper joachimschipper.nl> writes:
> Just untarring the release should work, but it's still odd. At least the
> md5sum of pfctl matches what I just downloaded, so that seems fine; did
> you actually use *that* tarball, though? (Note that the "right" pfctl
> binary is 500856 bytes long.)
[I consider it better to open a new thread, since the title, and part of
the content, of the previous one was superseded.]
Having upgraded one machine (amd64) from 4.6 to 4.7, using the normal
upgrade procedure as outlined in http://openbsd.org/faq/upgrade47.html
to the dot, after the reboot i
Joachim Schipper joachimschipper.nl> writes:
> Just untarring the release should work, but it's still odd. At least
> the md5sum of pfctl matches what I just downloaded, so that seems
> fine; did you actually use *that* tarball, though? (Note that the
> "right" pfctl binary is 500856 bytes lon
On 06/01/2010 05:32 AM, Philip Guenther wrote:
Was there a common thread to what did turn up? My recall is that
basically every time people get "Operation not supported by device"
errors from pfctl, it's because their userland and kernel don't match.
Review your upgrade procedure, because it
(I searched Google, but not much turned up.)
Since I upgraded to 4.7; what I get is:
# pwd
/etc
# cat pf.conf
# works?
# pfctl -f pf.conf.47
pfctl: DIOCBEGINADDRS: Operation not supported by device
# pfctl -f /etc/pf.conf
pfctl: DIOCXCOMMIT: Device busy
Huh?
(Actually I had used the original pf.
Uwe Dippel wrote:
It *must* be a mistake on my side, if the description on the OpenBSD
site is correct.
What can I do?
Let me add some remarks, after trying to debug it further:
Trying the install the conventional way results as to be expected on amd64:
qemu -m 32 -monitor stdio -no-fd
Rares Aioanei wrote:
On 04/28/2010 04:03 PM, Uwe Dippel wrote:
Trying to install a virtual OpenBSD on OpenBSD 4.6 on amd64, I did:
# env ETHER=em0 qemu -net nic,model=rtl8139 -net tap -m 32 -monitor
stdio -no-fd-bootchk -hda virtual.img \
-cdrom cd46.iso -boot d
as described in
http
Trying to install a virtual OpenBSD on OpenBSD 4.6 on amd64, I did:
# env ETHER=em0 qemu -net nic,model=rtl8139 -net tap -m 32 -monitor stdio
-no-fd-bootchk -hda virtual.img \
-cdrom cd46.iso -boot d
as described in
http://www.openbsd.org/cgi-bin/cvsweb/ports/emulators/qemu/files/README.OpenBS
Nick Holland wrote:
And in the end, a
'0'-sized bsd.sp after moving in a healthy bsd.mp.
I would not totally exclude an interference of this (new?) code that
lead to the described situation. Honestly, nothing at all done in that
session aside from what I wrote, between the 2 boots. I guess, not
Tobias Ulmer wrote:
As explained above, no, you likely moved around/corrupted /boot in a way
that doesn't work for biosboot.
Hmm. Actually I didn't. Through serial console, I had rebooted the
server, just 'to make sure', before booting to bsd.rd, and everything
went through. I rebooted ag
Having done upgrades from 4.0 onwards, on a OpenBSD-only server (amd64),
this time something must have gone wrong: Despite of the (remote, I have
no physical access, via serial console) 'successful' upgrade (no error
messages), when I was asked to reboot, I did, as always. Alas, it came
up wit
Johan Beisser wrote:
Read the man page for ssh_config(5) and sshd_config(5), and look at
restricting what your users can do.
Specifically: AllowTcpForwarding, PermitOpen and PermitTunnel,
combined with Match.
Thanks everyone for a great number of enlightening and helpful replies
to my po
Paul de Weerd wrote:
You could check for the presence of forwarded TCP sessions with fstat,
an exmaple looks like this :
weerdsshd 29016 11* internet stream tcp 0x40009ab33d0 127.0.0.1:44410
--> 127.0.0.1:3128
If you open an ssh session to a remote machine with a forwarded port,
t
Robert C Wittig wrote:
Have you considered adding a PF rule that would drop all incoming
login requests from this specific user?
Yes. But it won't work, because there is a NAT-address-rewrite in
between that changes the source address. Also, that user has plenty of
machines to log on to.
I
Paul de Weerd wrote:
tcpdump(8) will tell you a lot, I suppose ;) I guess the best way to
make sure the account is not compromised is talking to your user and
asking him if he can explain what is going on. Again, my current guess
is TCP forwarding, but it could be a lot of other things too. Ask
Iqigo Ortiz de Urbina wrote:
As its not clear to me if isuser is a user you trust, created or
needed for your services,
'Trusted', created by myself, needs a local account.
I would say your machine might have been compromised. What kind of
traffic is isuser generating?
Difficult to find o
Edd Barrett wrote:
Hi,
On Fri, Aug 21, 2009 at 6:54 AM, Uwe Dippel wrote:
Yes. Like
Accepted password for isuser from XXX.XX.XX.XX port 61802 ssh2
To be clear, the user exists, and logged on the last time three days ago as
far as 'last' is concerned.
This sounds very fish
Paul de Weerd wrote:
Hi Uwe,
Yes. Like
Accepted password for isuser from XXX.XX.XX.XX port 61802 ssh2
And this XXX.XX.XX.XX is the address of a machine you know ?
Yes
The user
is a well known user to you,
Yes
some system account perhaps ?
No
To be clear, the user e
Ryan Flannery wrote:
On Fri, Aug 21, 2009 at 1:19 AM, Uwe Dippel wrote:
Recently, I noticed an ssh user on one of my machines, who never logged on,
is not visible with 'last', seems to have no terminal active, and is back
immediately after a reboot.
Hmm.
root 13415 0.0 0.9
Recently, I noticed an ssh user on one of my machines, who never logged
on, is not visible with 'last', seems to have no terminal active, and is
back immediately after a reboot.
Hmm.
root 13415 0.0 0.9 3280 2420 ?? Ss12:04PM0:00.08 sshd:
isuser
isuser 702 0.0 0.7 3280 18
At least, that's what the website says at http://openbsd.org/46.html
True or typo? (I'd expect November 1st.)
Uwe
Jonathan Gray goblin.cx> writes:
> No, this will never be in 4.5. The acpi parser has changed significantly
> since 4.5 which made many hp machines much happier. You need
> to run a snapshot to get the newer parser to resolve this problem.
Correct, guys, thanks so much!
I ran the -cuurent of A
Jonathan Gray goblin.cx> writes:
> Nowhere do you state which release you are running. Similiar problems
> have been fixed in -current some months ago, so what are you running?
My fault. I'm running 4.5 stable. Would those fixes have made it into 4.5? If
yes, -current is no alternative. What ex
Uwe Dippel uniten.edu.my> writes:
>
> Marco Peereboom wrote:
> > we need a trace; this is worthless.
> >
>
> Thought so. Here are the screens, in the attachment.
> Hope, it goes through!
>
> Uwe
>
> [demime 1.01d removed an attachment of type i
Marco Peereboom wrote:
> we need a trace; this is worthless.
>
Thought so. Here are the screens, in the attachment.
Hope, it goes through!
Uwe
[demime 1.01d removed an attachment of type image/jpeg which had a name of
IMG_0623.JPG]
[demime 1.01d removed an attachment of type image/jpeg whic
What I did: Install into wd0, second DOS partition, 20G. Everything
looked good. At reboot, the panic happens, always.
ps is easy:
ddb> ps
* 0 -1 0 0 7 0x80200 swapper
ddb> trace
Debugger() at Debugger+0x5
panic() at panic+0x122
_aml_die() at _aml_die+0xdb
aml_xconvert() at aml_xconvert+0x68
[..
Janne Johansson it.su.se> writes:
> Isn't that the case with all fstab entries right now?
>
> You get the computer to list some drive before other disks, raid or no
> raid, and fstab breaks on you.
No, you didn't read it carefully enough. fstab breaks on me when I shove in a
drive 'before', tr
Uwe Dippel uniten.edu.my> writes:
> To me this seems a result of the sequence at boot: at first we identify the
> physical drives, that is sd0, sd1, sd2 and sd3 in this case, and only later
> do we get softraid up, sensibly roaming the RAID one up. Sensibly? Because
> fstab can&
Marco Peereboom peereboom.us> writes:
> > Next problem: There are quite a number of bays available in my box,
> > so that I can plug another drive for a local 'dump'. But irrespective
> > where I plug it, it won't come up:
>
> Your trace shows that it comes up just fine.
> > softraid0: volume
Marco Peereboom peereboom.us> writes:
> This is currently correct because I am working on this particular case.
> This one has proved to be very hairy hence it isn't in the tree yet.
Good to know, thanks for the heads-up, I keep waiting then for 4.6, I guess?
> > I'd expect the
> > softraid,
Marco Peereboom peereboom.us> writes:
>
> This is a repeat of the "can't bring up a raid set with missing
> members"
Yes, exactly. This can be closed; it was just to demonstrate that I am not
the only person, who sees broken mirrors being re-attached.
Marco Peereboom peereboom.us> writes:
>
> This one the pulled drive still contains the same metadata as the
> surviving members. Since you are running a home made kernel I have no
> idea what code you are running. This scenario should work with the code
> I committed a couple of weeks ago. Fr
Marco Peereboom peereboom.us> writes:
> > Then keep asking!
> > I do have the impression, what I wanted, is what you already had in mind:
> > a broken mirror simply remains dead and broken, and the machine runs
> > happily
> > before and after reboot on the sane drive. Correct?
>
> Correct.
Marco Peereboom peereboom.us> writes:
>
> > Then keep asking!
> > I do have the impression, what I wanted, is what you already had in mind:
> > a broken mirror simply remains dead and broken, and the machine runs
> > happily
> > before and after reboot on the sane drive. Correct?
>
> Correct.
Marco Peereboom peereboom.us> writes:
> Correct. If this isn't the case then I need to see a dmesg before &
> after rebooting and bioctl output before and after reboot.
This is as well supported by the post
http://vext01.blogspot.com/2007/11/playing-with-new-softraid-driver-in.html
"[...]
Bio
Marco Peereboom peereboom.us> writes:
> Correct. If this isn't the case then I need to see a dmesg before &
> after rebooting and bioctl output before and after reboot.
>
> Keep in mind that softraid can only detect failure AFTER an io fails.
> This is key, because you could fail a drive and g
Marco Peereboom peereboom.us> writes:
> Upon reboot the mirror should be brought up with only the surviving
> member. If this isn't the case please show me a trace so that I can go
> fix that bug.
'trace' means what here? Yes, I unplugged a drive of a working mirror as I
wrote, halt, plugged it
Marco Peereboom peereboom.us> writes:
> The plugging in of the disk is a non-event. The disk is dead to the
> OS and by extension to softraid.
Let me follow up on this topic, please, and report some more experiments and
results and thoughts.
I recreated the mirror from scratch, and put /tmp,
Stuart Henderson spacehopper.org> writes:
> Are you trying to boot an amd64 kernel? If so, you need qemu-system-x86_64.
Chances are, that I did. Downloaded the i386-cd45.iso, and followed the
'tap mode' path:
ifconfig tun0 link0
ifconfig bridge0 create
brconfig bridge0 add tun0 add bge0 up
All
Abel Camarillo the00z.org> writes:
>
> that escenario is explained in the README.OpenBSD installed with qemu.
Sorry, it still won't. It will segfault, though I follow the text (correctly,
and correct me if I am wrong):
So what I typed is:
# env ETHER=bge0 qemu -net nic,model=rtl8139 -net tap -
Abel Camarillo the00z.org> writes:
>
> that escenario is explained in the README.OpenBSD installed with qemu.
That's a really great hint! Thanks a bunch!
(Though it still looks like installation needs X:
"3. Install the os:
[...]
NOTE: start this inside an xterm or equivalent"
contrary t
I would like to set up a virtual/emulated OpenBSD machine on an existing
OpenBSD box; using qemu. The guest will only be accessible through the
network (ssh), under an address different from the host IP; though
through the same physical NIC.
I wonder if anyone has some experience or a link about
I tried again, setting up RAID1 on 2 U320 drives, 15k, as described in
softraid(4).
Now I find the speed to be too slow. Writing to a single file is kind of
okay: [everything/pwd is /mnt, which is a softraid drive, /dev/sd3f]
# bioctl sd3
Volume Status Size Device
softraid0 0 Onli
Raimo Niskanen erix.ericsson.se> writes:
> Does not really bioctl say nothing? Try "bioctl sd3"
> "bioctl softraid0", "bioctl -q sd3", "bioclt -q softraid0".
Thanks, the first two do it; fault was on my side. I did try the latter 2, and
both , well, I dunno what they tell me:
# bioctl -q sd3
sd
Marco Peereboom peereboom.us> writes:
> > Maybe I wasn't all too clear? My expectation is not (yet) the automatic
> > recovery of the respective half mirror! Sure not! I don't expect
> > miracles. What I do expect, though, is a consistent, defined and
> > predictable state.
>
> Your expect
Marco Peereboom wrote:
[push the disk back in]
Stale metadata, disk will remain unused from now on.
check
[pull the other disk]
You lose. all data is gone (for all intents and purposes).
check
# ls -l
total 4
-rw-r--r-- 1 root wheel 9 May 13 12:00 testo
Uwe Dippel uniten.edu.my> writes:
> Now I wonder what to do. Will a traditional fsck do, or do I have to
> recreate the softraid?
I guess, I can answer this myself, in the meantime:
I did the fsck of the softraid volume sd3a and sd3b
(the first one was clean, to be expected, the s
Beautyful, as it looks like!
I tried here on 2 300 GB U320, and the setup went through without any
warnings (?? most users encounter some?).
What I did was: (my system disk is sd0)
fdisk -iy sd1
fdisk -iy sd2
printf "a\n\n\n\nRAID\nw\nq\n\n" | disklabel -E sd1
printf "a\n\n\n\nRAID\nw\nq\n\n"
Vadim Zhukov wrote:
Do your clients have ability to connect to external hosts? If yes then
you should not even bother logging PHP mail() calls or such.
If outgoing connections are closed then you should have different system
users (i.e., different UIDs) for each client; otherwise it'll be ea
Matthew Weigel idempot.net> writes:
> Huh? I'm talking about the CMS itself authenticating to the SMTP server,
> and giving each application a single set of credentials.
chroot is the name, and isolation is the game.
> This should be set in
> the CMS's config files, much like database credent
Chris Bennett wrote:
This could be helpful, possibly. First, you can maintain a functional
mini_sendmail by putting a nother script at /bin/mini_sendmail, this
script could do some sort of logging and then pass things on to the real
mini_sendmail, located somewhere else, different (hidden) n
Matthew Weigel idempot.net> writes:
> Then you have grown your userbase too fast with a terrible setup, and now
> you're caught in the middle of fixing the problem or avoiding downtime.
Are you sure this is not a misunderstanding? When you host user accounts, on a
tight, default, setup of OpenBS
When dealing with web based submission, the best thing I have found is
to make sure the web based submission adds its own headers like what it
is and where the user came from and such so when diagnosing the problem
one can easily block based on that information. If there is an account
involved, yo
I'm running postfix as MTA on a machine with several CMS, on a chrooted
Apache. Recently, there is a huge number of spam being sent from there,
alas. When I scan the postfix-logs, all those come from 'root', meaning
they don't come through port 25. I run OpenBSD with mini-sendmail, and
now I w
This is the first time in years; and I wonder what might be wrong. I
am running OpenBSD 4.4, nothing specific. I have rotated the logs
daily through these years, with the script as below, and no problem
until today. The machine has an uptime of 50 days.
Still after the cron-ed logrotation this morn
> Slightly off-topic:
> Would it rather be perl committing all that memory or httpd?
add some instrumentation and you'll find out. symon can be good
for this sort of thing (you can have it monitor memory/cpu use of
specific processes at a frequent interval and graph them).
> Can this be prevente
Ted Unangst wrote:
You ran out of swap.
Thanks, Ted, for the fast reply and immediate insight. So it must have
to do with that perl-program, since what I usually see is something like:
Memory: Real: 107M/347M act/tot Free: 1637M Swap: 0K/2151M used/tot
Slightly off-topic:
Would it rather b
Dear all,
for the first time ever I had one of my production boxes crashing. And
that was just a few hours after I allowed one of my users ExecCGI in her
home, in the chrooted, default, Apache.
The user was deploying some perl-script.
Can anyone with insight please look at the trace and point
Yesterday I upgraded my last production box (remote) from 4.3 to 4.4.,
without any hitch, rebooted, and so forth.
Last night at some innocuous time, it stopped accepting incoming mail
(postfix). This morning, it did courier-imap well, until I used an
existing ssh-session like this:
# pwd
/usr
Uwe Dippel wrote:
Here after reboot I find the following:
# apachectl start
/usr/sbin/httpd:/usr/lib/libm.so.2.3: undefined symbol 'isinf'
/usr/sbin/httpd:/usr/lib/libm.so.2.3: undefined symbol 'isnan'
/usr/sbin/httpd:/usr/local/lib/php/libphp5.so: undefined symbol 'is
Here after reboot I find the following:
# apachectl start
/usr/sbin/httpd:/usr/lib/libm.so.2.3: undefined symbol 'isinf'
/usr/sbin/httpd:/usr/lib/libm.so.2.3: undefined symbol 'isnan'
/usr/sbin/httpd:/usr/local/lib/php/libphp5.so: undefined symbol 'isinf'
/usr/sbin/httpd:/usr/local/lib/php/lib
Kenneth R Westerback wrote:
This (untested) diff might help. Unfortunately I have no Solaris to
test against and I'm off to work now. Test reports welcome, or better
fixes.
You lack the Solaris, and my firewall lacks the sources and stuff, so I
can't compile there. But if the dhcpd is a simp
Here is what Stuart requested.
I hope the attachment goes through!
Uwe
12:10:18.698196 00:20:ed:df:a7:28 ff:ff:ff:ff:ff:ff 0800 342: 0.0.0.0.68 >
255.255.255.255.67: [udp sum ok] xid:0x8e0c275e vend-rfc1048 DHCP:DISCOVER
MSZ:1472 LT:4294967295 VC:83.85.78.87.46.105.56.54.112.99
PR:SM+DG+NS+HN+D
Deraj Puma wrote:
This same thing happened to me last night between me and my ISP. I
deleted /var/db/dhclient.leases.if and rebooted which worked.
No cigar.
Of course, I have no /var/db/dhclient.leases, but I did move
dhcpd.leases out of the way and rebooted. It was recreated, but no IP
dished
Robert Blacquiere wrote:
Missing info would be output from dhcpd in the /var/log/daemon. Please
grep there on dhcpd and send this. Also add the mac address of the
failing machine. This will give us atleast info about the request and
offers to this box.
Sure. It is a tad long, but maybe, maybe,
Robert Blacquiere wrote:
Missing info would be output from dhcpd in the /var/log/daemon. Please
grep there on dhcpd and send this. Also add the mac address of the
failing machine. This will give us atleast info about the request and
offers to this box.
Sure. It is a tad long, but maybe, maybe,
Theo de Raadt wrote:
Oh, we are supposed to ask? Please, get real. If you want to give us
all the information you can file a bug report. By now you should know
we won't bend over backwards to ask for information. You want this
fixed as much as we do.
Sorry, Theo,
the message to gnats is o
I read the upgrade guide, followed it, and have a 4.4-router in front of me.
Alas, it does not at all dish out an IP-address to an OpenSolaris client
(nv98). It used to do so before, without any fail at all, ever.
Immediately after the upgrade to 4.4, it fails 100%.
It does dish out IP-addresses
Uwe Dippel wrote:
4.2 runs out of the box, but with very slow access of files. The CF is
reasonably fast, though, with ~6MB at 'dd'. But once it has to access
files for r/w, it gets very slow.
Any hint welcome,
I got a really great hint. Let me start with the results:
tar -C /
[I read all postings in the archive AFAIK]
Just started with CF on embedded hardware advertised to run OpenBSD;
ARInfoTek. It does run OpenBSD very well!
Now I want the embedded system to run off CF; the board has a CF socket
to be wd0.
4.2 runs out of the box, but with very slow access of file
On Sun, 20 Jul 2008 20:19:05 +1000, Damien Miller wrote:
>> > My suspicion is that syslogd has not yet finished
>> > making the log socket and the "postfix check" that
>> > happens at postfix start fails.
>
> That shouldn't happen, because syslogd delays its exit until after
> its log sockets ha
On Mon, 14 Jul 2008 12:47:40 -0500, Karl O. Pinc wrote:
> I've an OpenBSD box that's been running postfix for a few
> years, strictly as a "send-only" mta, and every night the
> box gets rebooted. Every couple of months postfix does
> not come up on reboot.
>
> All that shows up in the logs is:
On Wed, 16 Jul 2008 19:41:55 +0700, sonjaya wrote:
> i have small ups seri APC / Back-UPS ES 525 , how to joint and control
> with openbsd , i try using apc-upsd when test not working.
> then i try nut but unknown driver.
> if any sucsess story can share to me :)
Yes, but not with ports, this
On Thu, 08 May 2008 09:41:23 +0800, Uwe Dippel wrote:
> Apache reacts very slow. Despite of a load <0.5,
> lynx 127.0.0.1 (as root) takes more than 5-10 seconds until the static
> -rwxr-x--- 1 root www 2236 Dec 12 2006 /var/www/htdocs/index.html
> props up. Any other task o
After the successful upgrade of the first machine, I have some trouble
with the second.
Chances are that the trouble is my fault, but I could still appreciate a clue:
Apache reacts very slow. Despite of a load <0.5,
lynx 127.0.0.1 (as root) takes more than 5-10 seconds until the static
-rwxr-x---
1 - 100 of 266 matches
Mail list logo
