[Spacewalk-list] info request list by a newbie

[William H. ten Bensel]

Item #1   - Taken directly from one of my spacewalks config

/etc/rhn/rhn.conf

#https://www.redhat.com/archives/spacewalk-list/2016-September/msg00016.html
# The number of days to wait to hear from a system before warning that it 
is not checking in.
web.system_checkin_threshold = 10

Item #2, I am not sure about that.


If you want to change more items, you can do the following in 
/etc/rhn/rhn.conf: 

Be aware of your hardware for these changes.  These are being applied to a 
system with 12 core CPU (24 hyper),  64G RAM, 10G network, Oracle DB 
running on a separate host.  Yes, overkill.

# The following overrides the defaults in 
/usr/share/rhn/config-defaults/*.conf
product_name = MY PRODUCT
java.custom_header = MY CUSTOM HEADER
java.config_file_edit_size = 128
web.maximum_config_file_size = 1048576
maximum_config_file_size = 1048576

# Now I know which of my spacewalks is having issues
web.default_mail_from = MY_SPACEWALK <root at mywalk.domain>

# this setting determines web session timeout- 20150416
web.session_cookie_lifetime = 28800
web.session_database_lifetime = 28800

# 
https://docs.oracle.com/cd/E92593_01/E71076/html/swk24-issues-memory.html 
-- 09/06/2016
taskomatic.java.initmemory=0
taskomatic.java.maxmemory=0
taskomatic.java.additional.1=-Xms1024m
taskomatic.java.additional.2=-Xmx12288m
taskomatic.logfile.maxsize=100m
java.taskomatic_channel_repodata_workers=4
#taskomatic.logfile.loglevel = DEBUG

# Increase rhn-search https://access.redhat.com/solutions/322093
# Increased from 2G to 4G - 09/06/2019
rhn-search.java.initmemory = 1024
rhn-search.java.maxmemory = 4096
rhn-search.logfile.maxsize = 100m

#rhn-search.logfile.loglevel = DEBUG
#rhn-seach.syslog.loglevel = DEBUG

# legal note to be displayed on the login page
# (join long lines with \, HTML is okay to use)
java.legal_note = BLAH BLAH BLAH BLAH.

# Satellite-sync failures
# https://access.redhat.com/solutions/179023
timeout = 600

Thanks and good luck




From:   gian sisal <giansisal19 at gmail.com>
To:     spacewalk-list at redhat.com
Date:   10/23/2019 04:09 AM
Subject:        [Spacewalk-list] info request list by a newbie
Sent by:        spacewalk-list-bounces at redhat.com



 
Hi everyone,
first: I'm using spacewalk 2.9.
I have two questions to pose:
1- I have "inactive systems" after 1 day, but for the systems I'm 
checking, maybe for maintenance or other reasons, I can have inactive 
systems for at least 2-3 days, spacewalk sends me notifications about 
systems I already know they are "inactive" (temporarily). Is there a way 
to tell spacewalk (portal configuration/server command line) to set 
"inactivity time"?

2- Related to the one above: I found a voice under "Systems --> duplicated 
systems" that says: 
**************************************************************************
 Inactive systems are listed below.
A system is inactive if its system has not checked in for  "1 days"
******************************************************************************
The part "1 days" is in drop-down list... other choices are "4 hours".."1 
month"... I tried to set "1 week" instead of "1 days" but the preference 
is not saved anywhere: I just switch and turn back to the section and 
again: "1 days". Is that normal? and above all: is this what I was looking 
for to answer the question above? last: is there a way to save this 
preference permanently?

Thanks for your cooperation and support.

Best Regards.
_______________________________________________
Spacewalk-list mailing list
Spacewalk-list at redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list



**

This email and any attachments may contain information that is confidential and/or privileged for the sole use of the intended recipient.  Any use, review, disclosure, copying, distribution or reliance by others, and any forwarding of this email or its contents, without the express permission of the sender is strictly prohibited by law.  If you are not the intended recipient, please contact the sender immediately, delete the e-mail and destroy all copies.
**
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20191023/5ad3dfba/attachment.htm>