Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Mint 20.1 on workstation, Debian 11 on servers
Posts: 1,336
Rep:
upsmon ignoring &>
When I start upsmon at startup, I want the output like "UPS START!!!!" and all that crap to go in an file, so I used &> but its still ignoring that, and still outputing to screen. Anyone know how to fix this?
I simply added a line in /etc/rc.d/rc.local to start a script called /data/scripts/start_os and in that script it calls UPSmon with the right parameters with &>/var/log/upsmon.log at the end of the command. So I really can't see why it aint working.
The upsmon program probably writes to syslog and not to either stdout or stderr, which you are capturing with &>. I'm not sure about the syslog specifics with FC, but you may want to check the man page for syslog.conf and look what type of messages are to be written to the console.
Distribution: Mint 20.1 on workstation, Debian 11 on servers
Posts: 1,336
Original Poster
Rep:
I tried that (good to know about that option btw, in case I get another program doing this) but its still insiting on outputing to the console.
The problem with this is, I have no way of knowing when and why the server shut down, if a power issue arrises and I'm not here. I need some kind of log to look at, but its just outputting it all to the console.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.