Sponsored Content
Full Discussion: Patch installation
Operating Systems Solaris Patch installation Post 302605754 by chetansingh23 on Thursday 8th of March 2012 12:02:18 PM
Old 03-08-2012
thanks a lot.... much helpful.. is there any way to be in touch with you on a regular basis for some knowledge sharing...
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Need Patch Installation Date

Can someone tell me how to get the installation date of a patch? I've done a showrev which I assume tells me if the patch cluster has been installed. It shows...SunOS 5.8 Generic 108528-23 June 2003. I'm assuming June 2003 is the patch release date. Is that right? How can I determine the... (1 Reply)
Discussion started by: kiloflash
1 Replies

2. Post Here to Contact Site Administrators and Moderators

Patch Installation

I am having trouble installing some HPUX patches on my 11.00. I am a novice at this so bear with me. I do not understand how to install depots. Now I'm trying to patch my system so I can get the Oracle client installed. Oracle says I need these two patches: PHSS_21950, QPK_11.00.64 I go to:... (0 Replies)
Discussion started by: RAFA
0 Replies

3. HP-UX

Patch Installation Problem

HI: Thanks for your help Im follow the steps describe on the link http://docs.hp.com/en/B2355-90772/ch06s01.html and have a diffetrent types of error messages and warning messages describes below: on the step two sh: PH* not found on step three *session started for user "root@test"... (0 Replies)
Discussion started by: RAFA
0 Replies

4. HP-UX

Patch Installation Problems

Hi people: I am having trouble installing some HPUX patches on my 11.00. I am a novice :confused: at this so bear with me. I do not understand how to install depots. Now I'm trying to patch my system so I can get the Oracle client installed. Oracle says I need these two patches:... (5 Replies)
Discussion started by: RAFA
5 Replies

5. Solaris

Patch installation quesiton

Hi, When we install patch on solaris box, if the server gets rebooted, do we need remove the patch and install? Or can we just re install? Please advise. (2 Replies)
Discussion started by: mokkan
2 Replies

6. Solaris

patch installation

Hey hi all, I just recently encountered these question regarding patch installation, the scenario is like these that i have three patches a,b,c and each of them require a server reboot.And I don't have to reboot the server three times..i can reboot it only once.. so what should i do ? Mine... (1 Reply)
Discussion started by: sahil_shine
1 Replies

7. Solaris

Patch Installation on Solaris10

Hi All, I am new to Solaris. I have to install some latest patches on my SPARC Machine running Solaris 10. I have installed the required patches. Please guide me through the rest of the process. Please include even minute details so that I don't face any problems while doing this activity. ... (12 Replies)
Discussion started by: kamaldeep1986
12 Replies

8. Red Hat

Patch Installation

Dear All, I have some 6 RedHat Servers ( 5.4 ) tikanga connected to the Intranet. Some are Database Servers and application servers. For the past 1.5 years , we have not installed any patches.. Is there any way to find out , whether these systems needs patches and where to... (5 Replies)
Discussion started by: jegaraman
5 Replies

9. Solaris

OS Patch Installation

Hello, I'm very new to this forum and solaris - I have solaris 5.10 installed on my machine (x86) and when I did a prerequisite check for Oracle Database 11g R2, it was showing the following patches are missing - OS Patch:137104-02 OS Patch:120754-06 OS Patch:119961-05 OS Patch:119964-14... (3 Replies)
Discussion started by: dsreedharan
3 Replies

10. Linux

Patch Installation

Am new to Linux and this forum From where can I download sysstatx86_64 and numactl-devel patches ? Thanks! :b: (1 Reply)
Discussion started by: dsreedharan
1 Replies
touch(1)							   User Commands							  touch(1)

NAME
touch, settime - change file access and modification times SYNOPSIS
touch [-acm] [-r ref_file | -t time] file... touch [-acm] [date_time] file... settime [-f ref_file] [date_time] file... DESCRIPTION
The touch utility sets the access and modification times of each file. The file operand is created if it does not already exist. The time used can be specified by -t time, by the corresponding time fields of the file referenced by -r ref_file, or by the date_time op- erand. If none of these are specified, touch uses the current time (the value returned by the time(2) function). If neither the -a nor -m options are specified, touch updates both the modification and access times. A user with write access to a file, but who is not the owner of the file or a super-user, can change the modification and access times of that file only to the current time. Attempts to set a specific time with touch will result in an error. The settime utility is equivalent to touch -c [date_time] file. OPTIONS
The following options are supported in the touch and settime utilities: touch The following options are supported for the touch utility: -a Changes the access time of file. Does not change the modification time unless -m is also specified. -c Does not create a specified file if it does not exist. Does not write any diagnostic messages concerning this condition. -m Changes the modification time of file. Does not change the access time unless -a is also specified. -r ref_file Uses the corresponding times of the file named by ref_file instead of the current time. -t time Uses the specified time instead of the current time. time will be a decimal number of the form: [[CC]YY]MMDDhhmm[.SS] where each two digits represent the following: MM The month of the year [01-12]. DD The day of the month [01-31]. hh The hour of the day [00-23]. mm The minute of the hour [00-59]. CC The first two digits of the year. YY The second two digits of the year. SS The second of the minute [00-61]. Both CC and YY are optional. If neither is given, the current year will be assumed. If YY is specified, but CC is not, CC will be derived as follows: +-----------------------------------------------------------+ |If YY is: CC becomes: | | 69-99 19 | | 00-38 20 | | 39-68 ERROR | +-----------------------------------------------------------+ The resulting time will be affected by the value of the TZ environment variable. If the resulting time value precedes the Epoch, touch will exit immediately with an error status. The range of valid times is the Epoch to January 18, 2038. The range for SS is [00-61] rather than [00-59] because of leap seconds. If SS is 60 or 61, and the resulting time, as affected by the TZ environment variable, does not refer to a leap second, the resulting time will be one or two seconds after a time where SS is 59. If SS is not given, it is assumed to be 0. settime The following option is supported for the settime utility: -f ref_file Uses the corresponding times of the file named by ref_file instead of the current time. OPERANDS
The following operands are supported for the touch and settime utilities: file A path name of a file whose times are to be modified. date_time Uses the specified date_time instead of the current time. This operand is a decimal number of the form: MMDDhhmm[YY] where each two digits represent the following: MM The month of the year [01-12]. DD The day of the month [01-31]. hh The hour of the day [00-23]. mm The minute of the hour [00-59]. YY The second two digits of the year. YY is optional. If it is omitted, the current year will be assumed. If YY is specified, the year will be derived as follows: +-----------------------------------------------------------+ |YY Corresponding Year | | 69-99 1969-1999 | | 00-38 2000-2038 | | 39-68 ERROR | +-----------------------------------------------------------+ If no -r option is specified, no -t option is specified, at least two operands are specified, and the first operand is an eight- or ten-digit decimal integer, the first operand will be assumed to be a date_time operand. Otherwise, the first op- erand will be assumed to be a file operand. USAGE
See largefile(5) for the description of the behavior of touch when encountering files greater than or equal to 2 Gbyte ( 2**31 bytes). ENVIRONMENT VARIABLES
See environ(5) for descriptions of the following environment variables that affect the execution of touch: LANG, LC_ALL, LANG, LC_ALL, LC_CTYPE, LC_MESSAGES, and NLSPATH. TZ Determine the timezone to be used for interpreting the time option-argument or the date_time operand. EXIT STATUS
The following exit values are returned: 0 The touch utility executed successfully and all requested changes were made. >0 An error occurred. The touch utility returned the number of files for which the times could not be successfully modified. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |CSI |enabled | +-----------------------------+-----------------------------+ |Interface Stability |Standard | +-----------------------------+-----------------------------+ SEE ALSO
time(2), attributes(5), environ(5), largefile(5), standards(5) NOTES
Users familiar with the BSD environment will find that for the touch utility, the -f option is accepted but ignored. The -f option is unnecessary because touch will succeed for all files owned by the user regardless of the permissions on the files. SunOS 5.10 22 Jun 2001 touch(1)
All times are GMT -4. The time now is 07:26 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy