Sponsored Content
Full Discussion: Patch management dilemma
Operating Systems Linux Red Hat Patch management dilemma Post 302352326 by flekzout on Friday 11th of September 2009 04:10:58 AM
Old 09-11-2009
yes, if ur server do not connect to internet, then u need to install it manually and apply it to ur servers.. its really bothering me as well, but if it's possible try to open the access-list from your router to allow it download from the redhat networks for a while then close it again. actually there is no use to patch the server when the server is not connected to internet. it only will bring an disaster and screw the systems of your server which is currently working fine. stupid auditors or security team makes this thing happened.
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

A Terminal Dilemma

Hi everyone, I hope this is the right place to ask this question... I have a contract to convert a mainframe/DB2 application to using AIX/Oracle. Everything went fine but we are now running into a terminal problem. With the Mainframe app, the clients had great response time from remote... (5 Replies)
Discussion started by: rocky_triton
5 Replies

2. UNIX for Advanced & Expert Users

linux patch management tool

I have a suse linux 9(SLES 9) I have configured "YOU" (yast online update) and it all working fine, synchronising on a daily base with http://sdb.suse.de/download but I would like to know if they is a tools or scripts that inform you of any patches that has not been applied and notify you via... (0 Replies)
Discussion started by: hassan1
0 Replies

3. Linux

Linux Patch Management

Does anyone know who to centrally manage the distribution and application of patches to multiple Linux platforms ? Is there software for this ? (0 Replies)
Discussion started by: jimthompson
0 Replies

4. Linux

Apache in enterprise, patch management

I was wondering how everyone else manages patching/upgrades for apache. Latest doesnt mean greatest, we typically dont install the newest patches for our OS's. We typically run 3-6 months behind, to let fixes get fixed before installing them. Does anyone here have a written detailed plan... (0 Replies)
Discussion started by: Ikon
0 Replies

5. UNIX for Advanced & Expert Users

Patch Management over mixed unix platforms

Does anyone know of any tools that manage the rollout of patches across multiple types of Unix platform ( eg Solaris, Aix etc ). I am looking for something that does a similiar job to SMS or WSUS in the Windows world (3 Replies)
Discussion started by: jimthompson
3 Replies

6. Solaris

Help needed regarding Solaris 10 patch Management

Hello Friends.. I have not tried anything related to Solaris patch and wish to learn more about it. I just wanted to try the patchadd and patchrm commands and how they work, just for educational purpose. I tried to download Solaris 10 patches, it asked me to register at sunsolve.com and i... (5 Replies)
Discussion started by: saagar
5 Replies

7. UNIX for Advanced & Expert Users

Multi-platform Centralized Patch Management

We have a mix of AIX, HP-UX, Linux (RHEL and SLES), and Solaris in our environment. Currently we have seperate patch management systems for each platform (NIM, SD, Spacewalk, etc), but have started looking for a centralized patch management solution that would work for most, if not all, of our... (0 Replies)
Discussion started by: kknigga
0 Replies

8. HP-UX

Patch Management

HI all, As per the audit policy, patch has to be apply periodically, but in my scenerio, it has been applied lastly in the year 2010. Using HP UX 11.11, 11.21 and 11.31 I would like to know, how to identify the patches which are need to update, what will be the procedure to update, how to... (5 Replies)
Discussion started by: selvaforum
5 Replies

9. Solaris

Patch management (Solaris, AIX , Linux )

Hi Guys, I am doing L1 Level support for Solaris Platform. Eg. User Management, File system , Print management and Job monitoring. I recently completer my IBM Aix 7 Administration certification. Issue is that my manager is asking me do full time unix / linux patch management work for new... (5 Replies)
Discussion started by: Nats
5 Replies
timed(8)						      System Manager's Manual							  timed(8)

Name
       timed - time server daemon

Syntax
       /usr/etc/timed [ -i | -n network ][ -E ][ -M ][ -t ]

Description
       The  daemon  synchronizes a host's time with the time of other machines in a local area network running It is normally invoked at boot time
       from the file.

       Servers running slow down the clocks of some machines and speed up the clocks of others to bring them all to the average network time.  The
       average	network  time is computed from measurements of clock differences with the Internet Communication Message Protocol (ICMP) timestamp
       request message.

       The service provided by is based on a master-slave scheme.  When is started on a machine, it asks the master for the network time and  sets
       the host's clock to that time.  After that, it accepts synchronization messages periodically sent by the master and calls the or routine to
       perform any corrections on the host's clock.

       It also communicates with the command to set the date globally, and with the control program, If the machine running  the  master  crashes,
       then  the  slaves  elect  a new master from among slaves running with the flag set.  The flag provides time synchronization on any attached
       networks where no current master server is detected.  Such a server propagates the time computed by the top-level  master.   At	least  one
       daemon on each network must run with the option set to allow it to become a master.

Options
       -E     Overrides  the input of slaves.  Use the flag in conjunction with the flag.  It specifies that a master should not average the times
	      of the slaves to calculate the network time but should distribute the time of its local host as the network time.  This flag  allows
	      a master to distribute time to a network while the network time is controlled by an outside agent such as the Network Time Protocol.

       [-i | -n] network

	      -i     Specifies	a  network  to ignore.	Each network that appears as an argument to the flag is added to the list of networks that
		     will ignore.  If the flag is used, accesses all networks to which the host is connected except for those  networks  specified
		     as arguments to the flag.

	      -n     Specifies a network to use.  When the is started, it gathers information about all the network devices connected to the local
		     host.  If neither the flag nor the flag is used, tries to access all the network devices connected to the	local  host.   The
		     network argument to the flag is the name of a network that should access.

		     If the switch is used, only those networks specified by the flag are accessed.

		     Do not use the and flags together.

       -M     Allows  a  slave	time  server to become a master time server if the master server crashes.  A system running the daemon without the
	      flag set remains a slave.  The daemon checks for a master time server on each network to which it is connected.	It  requests  syn-
	      chronization service from the first master server it locates.

       -t     Enables to trace the messages it receives in the file Tracing can be enabled or disabled with the program.

Restrictions
       Any  system  running with the and options set is eligible to become the master, and distribute its local time to all systems running on its
       network.  Run the Network Time Protocol daemon, instead of to prevent this behavior.

Files
       Invokes the			  daemon each time the system boots

       Tracing file for

       Log file for master

See Also
       date(1), adjtime(2), gettimeofday(2), networks(5), ntpd(8), timedc(8)
       Introduction to Networking and Distributed System Services

																	  timed(8)
All times are GMT -4. The time now is 04:47 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy