Re: OT: Helpdesk/Call tracking software
On Wednesday 20 July 2005 06:11 pm, Cezar Fistik wrote: Dear group, Sorry for OT, but I'm sure someone in this group can help me. I'm looking for an open source helpdesk/call tracking application for use in an ISP customer support dept. We need something that will allow us to register all incomming calls, to assign tasks to different admnis/engineers according to customer's problem, to be able to see the status of each opened issue and so on. Nothing unusual. A product I implemented for a company is called osTicket. It's completely open sourced and uses MySQL. I'm not sure if it's designed to track phone calls bu I don't see why not... but it's primary focus is as a web based ticket system. See http://www.osticket.com for more details. I made a search and found a number of such applications, but there are so many...it wouldn't be possible to test all of them. So please just tell me what you are using and how would you rate it. There's a lot of crap out there -- make sure you find something that's secure and _actively_ supported but it's developers. Thank you very much. Best of luck, - Justin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: can't figure out ssh, read lots of docs...
On Jun 01 05 05:57PM, Steven Friedrich wrote: snip What I did notice though, is that I can't login as root using ssh. I haven't found this mentioned in the man pages. Anybody know where it's documented, whether it can be changed, and would that be a colossal mistake? Again, if I may reiterate, it is highly dangerous to allow root login. Although if you _must_ know, you want to add: PermitRootLogin = Yes to your sshd_config file and then restart sshd. Beware! I mean, hey, it's a secure shell, why can't I login as root? The reason I want to use root is because I'm trying to scp /etc/master.passwd from each of my four machines so I can write them to a CD for backup. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] - j pgpIunnbzgcu3.pgp Description: PGP signature
Re: Adding my CDRW device to k3b
On Apr 20 06:54PM, Michael Collette wrote: Before getting into the CDRW stuff, why K3B wouldn't run. I would bet that you're using an X Display Manager, like kdm, gdm, or even xdm. You can't just su into root and run stuff like that. You need to fully log out, then log into whatever wm you use as root. When you do that, k3b should come up just fine. I log into my system as root then launch kdm then log in as myself. What do you recommend I do, log into kdm as root? Is there any way to get k3b running under a normal user account? But it still probably won't pick up the devices :( Oh, if life were simpler in FreeBSD land. First off, check that the following lines exist in your kernel config... device scbus # SCSI bus (required for SCSI) device ch # SCSI media changers device da # Direct Access (disks) device sa # Sequential Access (tape etc) device cd # CD device pass# Passthrough device (direct SCSI access) device ses # SCSI Environmental Services (and SAF-TE) device atapicam Especially important is that last one, as it ain't in the GENERIC kernel last I checked. That's the magical beast that'll get it all playing. Get that in there and recompile your kernel. You might get away with kldload cam, but I honestly don't know if that's the same thing. I was missing a few of the above items: sa, ses, and ch. My new kernel is compiling now. Then you'll want to get permissions and links all setup proper every time you boot in. Here you'll need to get /etc/devfs.conf all tweaked up proper for normal users. # /etc/devfs.conf permacd00666 linkacd0cdrom linkacd0dvd permpass0 0666 permcd0 0666 permxpt00666 You may want to instead link cd0 to cdrom and dvd, but these settings seem to work for me here. Took care of this as well. I don't recall seeing anything about editing devfs.conf in the handbook. Perhaps I overlooked it. Make sure your /etc/rc.conf has the line... devd_enable=YES This is default in newer versions of FreeBSD. Doesn't hurt to toss it in there thought. All set now with this as well. The k3b port will have installed cdrdao, but it wouldn't have tweaked on it's permissions. This one you'll most likely want to make it suid root. Definitely not something you'd want to do on a production server box just out of paranoia, but reasonably safe on a desktop. # As root cd /usr/local/bin chmod u+s cdrdao I stumbled upon these while researching my problem. Double checked the above and it looks good. After jumping through all those fun loving hoops, it should work shweet. In fact, k3b will automatically add your CD into the device list. If k3b didn't put it in there for you, that's a clue that something isn't right. I'm waiting for my new shiny kernel and we will see what happens! Thanks so much for your help Michael! I look forward to making some illegitimate music CDs and driving around dodging the law! :D Good luck! On 4/14/05, Justin R. Pessa [EMAIL PROTECTED] wrote: Allo! I'm having problems trying to get k3b to recognize my CDRW drive. I went to Settings COnfigure k3b Devices. When I add /dev/acd0 it says Could not find an additional device at /dev/acd0. Here is the output of dmesg. The system sees the device fine, I folloed the handbook instructions for CDRW setup. acd0: CDRW TDK CDRW241040X/6.34 at ata1-master PIO4 cd0 at ata1 bus 0 target 0 lun 0 cd0: TDK CDRW241040X 6.34 Removable CD-ROM SCSI-0 device cd0: 16.000MB/s transfers cd0: cd present [1 x 2048 byte records] $ ls -al /dev/acd0 crw-rw-rw- 1 root jstn4, 13 Apr 7 22:14 /dev/acd0 I realize this is probably more a k3b problem than a FreeBSD problem, but I feel as though there is something specific to FreeBSD I have either missed or am over looking. Any ideas? Thanks! ._ | Justin R. Pessa | http://jstn.sdf1.org -- When you come to a fork in the roadTake it - Yogi Berra Warm Regards, - j .__. | Justin R. Pessa - BOFH | www: http://jstn.sdf1.org | pgp: http://jstn.sdf1.org/pgp.html | irc: asdf @ irc.freenode.net ' pgpQeP5oC7gks.pgp Description: PGP signature
Re: Adding my CDRW device to k3b
Seems like the suggestions below worked like a charm! I'm burning a CD as we speak, thanks a lot! On Apr 20 05 06:54PM, Michael Collette wrote: Before getting into the CDRW stuff, why K3B wouldn't run. I would bet that you're using an X Display Manager, like kdm, gdm, or even xdm. You can't just su into root and run stuff like that. You need to fully log out, then log into whatever wm you use as root. When you do that, k3b should come up just fine. But it still probably won't pick up the devices :( Oh, if life were simpler in FreeBSD land. First off, check that the following lines exist in your kernel config... device scbus # SCSI bus (required for SCSI) device ch # SCSI media changers device da # Direct Access (disks) device sa # Sequential Access (tape etc) device cd # CD device pass# Passthrough device (direct SCSI access) device ses # SCSI Environmental Services (and SAF-TE) device atapicam Especially important is that last one, as it ain't in the GENERIC kernel last I checked. That's the magical beast that'll get it all playing. Get that in there and recompile your kernel. You might get away with kldload cam, but I honestly don't know if that's the same thing. Then you'll want to get permissions and links all setup proper every time you boot in. Here you'll need to get /etc/devfs.conf all tweaked up proper for normal users. # /etc/devfs.conf permacd00666 linkacd0cdrom linkacd0dvd permpass0 0666 permcd0 0666 permxpt00666 You may want to instead link cd0 to cdrom and dvd, but these settings seem to work for me here. Make sure your /etc/rc.conf has the line... devd_enable=YES This is default in newer versions of FreeBSD. Doesn't hurt to toss it in there thought. The k3b port will have installed cdrdao, but it wouldn't have tweaked on it's permissions. This one you'll most likely want to make it suid root. Definitely not something you'd want to do on a production server box just out of paranoia, but reasonably safe on a desktop. # As root cd /usr/local/bin chmod u+s cdrdao After jumping through all those fun loving hoops, it should work shweet. In fact, k3b will automatically add your CD into the device list. If k3b didn't put it in there for you, that's a clue that something isn't right. Good luck! On 4/14/05, Justin R. Pessa [EMAIL PROTECTED] wrote: Allo! I'm having problems trying to get k3b to recognize my CDRW drive. I went to Settings COnfigure k3b Devices. When I add /dev/acd0 it says Could not find an additional device at /dev/acd0. Here is the output of dmesg. The system sees the device fine, I folloed the handbook instructions for CDRW setup. acd0: CDRW TDK CDRW241040X/6.34 at ata1-master PIO4 cd0 at ata1 bus 0 target 0 lun 0 cd0: TDK CDRW241040X 6.34 Removable CD-ROM SCSI-0 device cd0: 16.000MB/s transfers cd0: cd present [1 x 2048 byte records] $ ls -al /dev/acd0 crw-rw-rw- 1 root jstn4, 13 Apr 7 22:14 /dev/acd0 I realize this is probably more a k3b problem than a FreeBSD problem, but I feel as though there is something specific to FreeBSD I have either missed or am over looking. Any ideas? Thanks! ._ | Justin R. Pessa | http://jstn.sdf1.org -- When you come to a fork in the roadTake it - Yogi Berra - j .__. | Justin R. Pessa - BOFH | www: http://jstn.sdf1.org | pgp: http://jstn.sdf1.org/pgp.html | irc: asdf @ irc.freenode.net ' pgpLiqaWKZqiw.pgp Description: PGP signature
Re: Stability problems with 5.3-Release
On Apr 21 05 06:22PM, Chris McGee wrote: I've got 2 identical boxes (Supermicro sys-6023P-8R) running with ZCR adaptec cards with 6 73Gig seagate scsi drives, 4 Gigs of ram, and dual 2.4 Ghz Xeons. Both of these machines are running 5.3-Release-p8. The usually run for a day, give or take, and then they crash. The just deadlock, no console response, no nothing. The get power cycled and they are fine for a little while again. These are configured to be mysql database servers. I can provide any information necessary, but i'm stumped and it's causing me a lot of heartache now. I've had similar problems as well. One thing I noticed is that a process may get hung in the D state and never returns. From there it seems the system enters a downward spiral and everything locks up. I've had this problem with p6 and p7. Attached is my dmesg output. Not sure if it's helpful... I can't offer anything in the form of a solution but figured I'd chime in so that Chris doesn't think he's the only (crazy) one with this problem! ;) Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] - j .__. | Justin R. Pessa - BOFH | www: http://jstn.sdf1.org | pgp: http://jstn.sdf1.org/pgp.html | irc: asdf @ irc.freenode.net ' Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.3-RELEASE-p7 #3: Thu Apr 21 13:24:51 EDT 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/TWINTURBO Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 1700MHz (1707.56-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf0a Stepping = 10 Features=0x3febf9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM real memory = 268349440 (255 MB) avail memory = 257130496 (245 MB) npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface acpi0: ASUS P4T on motherboard acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0xe408-0xe40b on acpi0 cpu0: ACPI CPU (2 Cx states) on acpi0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: Intel 82850 host to AGP bridge mem 0xf800-0xfbff at device 0.0 on pci0 pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 pci1: display, VGA at device 0.0 (no driver attached) pcib2: ACPI PCI-PCI bridge at device 30.0 on pci0 pci2: ACPI PCI bus on pcib2 pcm0: Creative EMU10K1 port 0xd800-0xd81f irq 9 at device 6.0 on pci2 pcm0: SigmaTel STAC9708/11 AC97 Codec rl0: RealTek 8139 10/100BaseTX port 0xd000-0xd0ff mem 0xf180-0xf18000ff irq 9 at device 11.0 on pci2 miibus0: MII bus on rl0 rlphy0: RealTek internal media interface on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: Ethernet address: 00:02:2a:b3:24:a0 isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel ICH2 UDMA100 controller port 0xb800-0xb80f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 uhci0: Intel 82801BA/BAM (ICH2) USB controller USB-A port 0xb400-0xb41f irq 9 at device 31.2 on pci0 uhci0: [GIANT-LOCKED] usb0: Intel 82801BA/BAM (ICH2) USB controller USB-A on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ums0: KYE Genius USB Wheel Mouse, rev 1.00/0.00, addr 2, iclass 3/1 ums0: 3 buttons and Z dir. pci0: serial bus, SMBus at device 31.3 (no driver attached) uhci1: Intel 82801BA/BAM (ICH2) USB controller USB-B port 0xb000-0xb01f irq 9 at device 31.4 on pci0 uhci1: [GIANT-LOCKED] usb1: Intel 82801BA/BAM (ICH2) USB controller USB-B on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered fdc0: floppy drive controller port 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: 1440-KB 3.5 drive on fdc0 drive 0 ppc0: ECP parallel printer port port 0x778-0x77a,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: Parallel port bus on ppc0 sio0: 16550A-compatible COM port port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: 16550A-compatible COM port port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] orm0: ISA Option ROMs at iomem 0xcc000-0xc,0xc-0xcb7ff on isa0 pmtimer0 on isa0 sc0: System
Adding my CDRW device to k3b
Allo! I'm having problems trying to get k3b to recognize my CDRW drive. I went to Settings COnfigure k3b Devices. When I add /dev/acd0 it says Could not find an additional device at /dev/acd0. Here is the output of dmesg. The system sees the device fine, I folloed the handbook instructions for CDRW setup. acd0: CDRW TDK CDRW241040X/6.34 at ata1-master PIO4 cd0 at ata1 bus 0 target 0 lun 0 cd0: TDK CDRW241040X 6.34 Removable CD-ROM SCSI-0 device cd0: 16.000MB/s transfers cd0: cd present [1 x 2048 byte records] $ ls -al /dev/acd0 crw-rw-rw- 1 root jstn4, 13 Apr 7 22:14 /dev/acd0 I realize this is probably more a k3b problem than a FreeBSD problem, but I feel as though there is something specific to FreeBSD I have either missed or am over looking. Any ideas? Thanks! ._ | Justin R. Pessa | http://jstn.sdf1.org pgp0aN5DiiTrk.pgp Description: PGP signature
Re: Adding my CDRW device to k3b
On Apr 15 12:06AM, nbco wrote: On Friday 15 April 2005 00:00, Justin R. Pessa wrote: Allo! I'm having problems trying to get k3b to recognize my CDRW drive. I went to Settings COnfigure k3b Devices. When I add /dev/acd0 it says Could not find an additional device at /dev/acd0. snip I realize this is probably more a k3b problem than a FreeBSD problem, but I feel as though there is something specific to FreeBSD I have either missed or am over looking. Have you tried running k3b as root, if it sees your device as root. When I run an X app as root I get: Password: [EMAIL PROTECTED] /home/jstn $ k3b Xlib: connection to :0.0 refused by server Xlib: No protocol specified k3b: cannot connect to X server :0.0 I'm not sure how to give root permission to the X session on this display. Any thoughts here? Then you can change the permissions for the devices or just run it as root hope this helps .nbco Thanks! - j ._ | Justin R. Pessa | http://jstn.sdf1.org pgpdqGb6bhggH.pgp Description: PGP signature
Binary linking/updating libraries
How do I relink a binary against a library after I have updated the lib? For example I updated glib and now xchat complains about the library not being installed as it was linked against the old version. Is there any utility that can see which executables have library problems and relink them accordingly? Thanks in advance, - j ._ | Justin R. Pessa | http://jstn.sdf1.org pgpgs0VzRS33k.pgp Description: PGP signature
Re: Binary linking/updating libraries
On Apr 10 04:12PM, Kris Kennaway wrote: On Sun, Apr 10, 2005 at 07:08:47PM -0400, Justin R. Pessa wrote: How do I relink a binary against a library after I have updated the lib? For example I updated glib and now xchat complains about the library not being installed as it was linked against the old version. Is there any utility that can see which executables have library problems and relink them accordingly? In general this is the wrong thing to do. If a library changes version, it's usually because it's no longer compatible with the old version of the library, and applications that use it need to be recompiled or they may no longer run properly. Alternatively, if you upgrade using portupgrade, the old library will be preserved so that existing applications will not be affected. Kris Not what I wanted to hear but I appreciate your help! ;) I'll tinker with portupgrade and cross my fingers! Thanks, - j ._ | Justin R. Pessa | http://jstn.sdf1.org pgpRvaeM9Ww0D.pgp Description: PGP signature
