| |
| |
| |
|
Page: 1 2
Comments:
<0> Anyone know how zencart's email function should be configured on OpenBSD+ApacheChroot. I'm having problems getting it working, the choices are PHP, sendmail, sendmail -f, SMTPAuth, I'm running postfix on the same box as my MTA. When I set it to use PHP it says: cannot instanciate mail function
<0> when I set it to use sendmail it doesn't give me an error message but my /var/log/maillog shows no outbound activity
<1> hi there
<1> I'm brand new to OpenBSD and Ports, and I am wondering if there is a way to utilize ports w/o being root.
<1> Can I just give a prefix to make or something?
<1> ie. cd /usr/ports/sysutils/colorls;make $PREFIX=~
<2> i really doubt it
<2> you could try setting things like LOCALBASE
<2> no, it won't even work
<2> it won't be able to install anything
<2> you can build something from ports as non-root
<2> but not install it
<1> how do you build from ports as non-root?
<1> I don't have write access to the ports directory
<2> well, the easiest way is to copy the port you want to your home
<2> and build it there
<2> you can also probably play games with variables
<2> look at ports(7) and bsd.port.mk(5)
<1> thank you, Nic. I'l l examine the pages now
<1> hrm... ports makefiles try to write to /usr/ports/distfiles
<1> copying the dir to home doesn't work
<1> Is there a source repository that I could browse somewhere, instead?
<1> 3.7 i86
<1> n/m http://dir.filewatcher.com/d/OpenBSD/3.7/i386/colorls-3.5.1.tgz.142605.html
<2> set DISTDIR
<3> daniel
<4> say his nick, maybe the client he uses is set to beep when you say it
<3> thnaks for the tip.. i'll write that down
<5> i think binfalse just broke my sarcasim detector.
<5> *sarcasm, even.
<6> pkill <program> and kill -9 PID are ineffective for a misbehaving program, anything else I should/can do to terminate the process
<2> no
<2> i bet it's a zombie
<2> well, it could be
<2> or it could be stuck in the kernel
<2> ps will tell you if it is a zombie
<6> only other recurse is reboot then?
<6> recourse
<2> well, if its a zombie, kill its parent
<2> or ignore it, since it isn't doing any harm
<6> it is disklabel, and is keeping me from using it to check a drive
<2> what does ps say?
<2> is it a zombie or is it stuck?
<7> ps -ax | grep disklabel, the third field
<6> ps STAT is D
<6> what to do
<2> its stuck waiting in the kernel
<2> Ficus, thanks
<6> anything I can do to terminate it short of a reboot?
<2> no, but you probably want to figure out why its doing that
<2> or at least check if you have any disk errors
<6> dunno what else to look at, no errors are poping up in messages and such
<2> how did it get like that?
<2> what did you do with disklabel?
<6> disklabel /dev/sd0i
<2> and it just hung?
<6> ayup
<2> any messages added to dmesg?
<6> anope
<2> well, i dunno then ;_)
<2> in any case, the only way to get rid of it if it doesn't recover on its own is to reboot
<7> or unplug that pesky usb stick
<2> it won't get any signals including -9 until it exits the kernels
<2> kernel
<2> yeah, did you try unplugging the thing?
<2> of course sd0i must be usb...
<6> oh yes, an hour ago
<2> heh
<7> you can reboot, but if you plug it in again, you might end up like this again ;)
<6> so I guess I did/checked everything I could
<6> bizarro
<6> well knowing that you guys dunno either, is strangle comforting
<6> heh
<2> well, it's not that bizarre, it's some kind of bug
<6> I suppose
<2> something happened when it was waiting for something from the stick
<2> and it never got it
<7> don't plug in usb devices into mission-critical servers ;)
<2> and its still waiting
<6> it isn't mission critical at all, I just wouldn't think techniques used for windows applied to openbsd :-)
<6> i.e., reboot it
<2> for most things, true
<6> yah, tis no biggy in this case, mostly just distrubing for the "what if that happend, and you could just reboot it" scenario
<6> yah, tis no biggy in this case, mostly just distrubing for the "what if that happend, and you couldn't just reboot it" scenario
<6> sorry
<6> sort of a critical typo there
<6> dunno if it matters, but this is on a 4.0 box
<6> sh*t, just found out that this drive had a BIOS p***word installed on it, I am gonna go clobber my coworker now.
<8> How can a drive have a bios p***ord ? :P
<2> hmm?
<2> IDE disks can be p***worded
<9> ?
<9> how?
<2> atactl(8)
<2> don't forget the p***word though
<9> and, can one pendrive have a p***word?
<6> Sorry, a hard drive p***word set in the BIOS, which presumably does something to the drive at a pretty low level, since it was not mountable when remove from the machine without first removing the HD p***word. The drive has been put back into the original machine, p***word removed, drive removed and put into new machine, and its mountable now. Yes, I have brow beat my coworker for not telling me about this first
<2> probably the same thing
<2> ATA p***word
<2> debugg, don't think so
<6> is proprietary cypto used to do this I wonder? send the drive mach to MFG to unlock it? or are there other ways around this?
<2> i don't think its crypto at all
<2> you can get around it by swapping the controller PCB
<2> its just the enforced by the controller
<6> and say one didn't have a matching PCB, what then?
<9> sorry
<9> any one have idea why i get this error?
<9> http://rafb.net/p/5LK7F926.html
<10> mixing versions?
<9> nop
<9> i'm using -current
<11> refresh from cvs.
<9> yep
<10> debugg: what's kern.version?
<9> is update
<9> one second
<10> is your userland updated correctly?
<9> i think yes
<10> are you pulling the -current CVS correctly?
<9> humm
<9> my kern.bversion is:
<9> # sysctl kern.version
<9> kern.version=OpenBSD 4.0-current (GENERIC) #774: Tue Dec 12 20:57:03 MST 2006 deraadt@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
<10> that's a bit old
<10> grab a recent snapshot
<9> then, i need to update from the CVS src ?
<10> < lt_kije> grab a recent snapshot
<9> and recompile the system ?
<10> or update via CVS
<9> humm, ok
<10> updating with a snapshot is faster and (imho) easier
<9> many thx
<9> thx lt_kije , i'll update from snapshots
<11> debugg: one should always keep kernel, userland, ports, and optionally X in sync with each other. Your ports tree is up to date, but your kernel is old. :)
<9> ok
<11> since you're moving up from December, be sure to read the "following current" FAQ, as you have things you must do to move forward .... unless you just install the most recent snapshot.
<10> even then, you'll need to run mergemaster and figure out what's changed
<11> if you upgrade from a recent snapshot, you will still need to update things in /etc.
<11> and mergemaster is a great tool to help automate that.
<11> lt_kije and I think alike.
<4> http://groups.google.com/group/renolug/web/distribution-wars "Theo is an ***hole and the OS benefits greatly from it."
<2> baggy, then you are stuck
<6> NicM: good, that is what I wanted to see, otherwise the HD p***word locking would be completely useless
<6> anyone know how to get the headphone jack working? I have setup openbsd 4.0 on for different machines, and the speaker jack sound works on all of them, no sound for any of the via the headphone jack. All four are different types of Dell Machine two are laptops athe other two are desktops. The posts I found mention the same problem, but no solutions.
<10> mixerctl?
<10> prolly need to unmute iot
<10> *it
<6> sheesh, thanks "mixerctl -w ouputs.headphone.mute=off" did the trick... how do I set that permanently, so I don't have to do the same thing again after a reboot?
<10> mixerctl.conf(5)
<6> duh, sorry
<6> thanks again
Return to
#openbsd
or
Go to some related
logs:
#nhl
bash.org portuguese
dos2c64
#eggtcl
orion106
#beginner
qmailmrtg rblsmtpd
#computers
#mirc
lordpil
|
|