search for: cuaa1

Hi, I'm running into an issue while using FreeBSD 5.4, NUT from ports (2.0.3), serial on /dev/cuaa1, Ellipse 1200 USBS. The ups.conf is : [ellipse] driver=mge-utalk port=/dev/cuaa1 desc="Telecom Closet Ellipse" When I go to start it I get : Network UPS Tools - UPS driver controller 2.0.3 Network UPS Tools - MGE UPS SYSTEMS/U-Talk driver 0.87 (2.0.3) Could...

Hi, FreeBSD 5.4, NUT from ports (2.0.3), serial on /dev/cuaa1, Ellipse 1200 USBS. I set the ups.conf up as : [ellipse] driver=mge-utalk port=/dev/cuaa1 desc="Ellipse" When I go to start it I get : Network UPS Tools - UPS driver controller 2.0.3 Network UPS Tools - MGE UPS SYSTEMS/U-Talk driver 0.87 (2.0.3) Could not g...

...k UPS Tools - UPS driver controller 2.0.5 Network UPS Tools - MGE UPS SYSTEMS/U-Talk driver 0.88 (2.0.5) .Detected Pulsar ESV11+ on /dev/cuaa0 Network UPS Tools - Best UPS driver 1.03 (2.0.5) Unknown model detected - please report this ID: 'SOLA' Detected Unknown Unknown SOLA (SOLA) on /dev/cuaa1 Starting nut. Network UPS Tools upsd 2.0.5 Connected to UPS [mge]: mge Connected to UPS [sola]: sola -------------------------------- The mge is on but I can not get the sola to work as it should A copy of ups.conf bellow: ----------------------------- [mge] driver = mge-utalk por...

Hi, All ! I'm trying to use nut 2.0.5 on FreeBSD 4.11-STABLE with UPS INELT Monolith II 1000LT UPS connected to box with RS-232 cable. In ups.conf: [apc] driver = megatec port = /dev/cuaa1 desc = "UPS" When starting /usr/local/etc/rc.d/nut.sh start got: Network UPS Tools - UPS driver controller 2.0.5 Network UPS Tools - Megatec protocol driver 1.5 (2.0.5) Carlos Rodrigues (c) 2003-2006 Megatec protocol UPS not detected. Driver failed to start (exit status=1) How to so...

...sages from may 15, may 16 and may 17 here!** So it probably was caused by the serial console :). Doesn't the -P flag on /boot.config takes care of "telling" the rest of the system that now the console is a serial one? Having ttyd1 on /etc/ttys doesn't work for me, had to use cuaa1 instead, to have a working serial console. Maybe this cause the bug? Santos

Hey *, I'm getting an audit coming down the pipes and I have 2 4.6 release boxes to clean up. I say "clean up" because they have some requirements that I missed despite due diligence. My specific question is: To what extent can I get rid of UUCP? Aside from the SUID/SGID stuff that pops up via my finds, I simply see no reason to have any UUCP stuff on these boxes. Is this stuff

...; "Default" = "-adobe-helvetica-" "DefaultFixed" = "fixed" "DefaultSerif" = "-adobe-times-" "DefaultSansSerif" = "-adobe-helvetica-" [serialports] "Com1" = "/dev/cuaa0" "Com2" = "/dev/cuaa1" "Com3" = "/dev/cuaa2" "Com4" = "/dev/cuaa3" [registry] "LoadGlobalRegistryFiles" = "Y" "LoadHomeRegistryFiles" = "Y" "LoadWindowsRegistryFiles" = "Y" "WritetoHomeRegistryFiles" = &q...