Solution accepted Post: 302226589

6 More Discussions You Might Find Interesting

1. Solaris

MAILTO Not Accepted In Crontab

I have 3 solaris 9 servers 1 allows me to use MAILTO in the crontab, but the other 2 dont. Error MAILTO=oracle crontab: error on previous line; unexpected character found in line. crontab: errors detected in input, no crontab file generated. Any Ideas??

2. Forum Support Area for Unregistered Users & Account Problems

Password reset not being accepted

Why would a password reset, a provided numerical value thru email, not be accepted when trying to log in with it? I have expired the 5 login attempts twice with still no acceptance. thanks for the help

3. Solaris

Password accepted but kicked out

The Sun Solaris x86 system seemed to accept my username and password when I do SSH, but then the login prompt went away or hang. What happened?

4. Shell Programming and Scripting

Quick edit on accepted variable.

I am new newbie to unix. I am taking user input using ksh script. The valid value user can enter is a) Numeric 1 to 500 b) character e, r c) e1 to e100 I figured out how to deal with a) and b) but want to separate characters when user enter e1 to e100 I want to store e in...

5. Shell Programming and Scripting

Shell script : value under 1 (0,0...) is accepted as 0?

Hi all,, I have this script ctr=$(( 1/1000 )) while do echo $ctr >> test.txt doneHowever, it puts 0 instead of 0.001 How can I put 0.001 in the text file? Thank you

6. Cybersecurity

Certificates accepted/rejected depending on what service I use...

Hey everyone. I was at my local star bucks, which has open free wifi. And I (against my better judgement) deceided to check my school email. I was using their wifi network. when I went to go login, I was presented with the safari prompt "Can not Verify Server identity". I clicked 'details' and...

LEARN ABOUT MINIX

richcomm_usb

RICHCOMM_USB(8) 						    NUT Manual							   RICHCOMM_USB(8)

NAME

       richcomm_usb - Driver UPS equipment using Richcomm dry-contact to USB solution

NOTE

       This man page only documents the specific features of the richcomm_usb driver. For information about the core driver, see nutupsdrv(8).

SUPPORTED HARDWARE

       The Richcomm dry-contact to USB solution is a generic interface that is used to upgrade an existing (RS-232) contact closure UPS interface
       to USB. As such, all the limitations of the underlying contact closure interface apply. This means that you will only get the essentials in
       ups.status: OL, OB, and LB. See also genericups(8).

BUGS

       Most contact-closure UPSes will not power down the load if the line power is present. This can create a race when using slave upsmon(8)
       systems. See the upsmon(8) man page for more information.

       The solution to both of these problems is to upgrade to a smart protocol UPS of some kind that allows detection and proper load cycling on
       command.

AUTHORS

       Peter van Valderen <p.v.valderen at probu.nl>, Dirk Teurlings <dirk at upexia.nl>

SEE ALSO

   The core driver:
       nutupsdrv(8)

   The generic serial driver:
       genericups(8)

   Internet resources:
       The NUT (Network UPS Tools) home page: http://www.networkupstools.org/

Network UPS Tools						    05/21/2012							   RICHCOMM_USB(8)