Sponsored Content
Top Forums UNIX for Advanced & Expert Users UFSDUMP & UFSRESTORE problems Post 62538 by DGoubine on Thursday 17th of February 2005 02:08:08 AM
Old 02-17-2005
Hi, thanks for the answer.
What I don't understand is that I am supposed to have full permissions to the disks and this should not be happenning.
When I am trying to create a file by using "touch", I can do it being superuser, but not a regular user.
What do I do next ? Thanks !
Smilie
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

ufsdump/ufsrestore problem

I ran ufsdump as follows............... # ufsdump 9ucf /dev/rmt/0n /dev/dsk/c1t9d0s3 DUMP: Writing 63 Kilobyte records DUMP: Date of this level 9 dump: Tue 23 Oct 2007 02:19:40 PM PDT DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/rdsk/c1t9d0s3 (gambler:/apps) to... (2 Replies)
Discussion started by: shorty
2 Replies

2. Solaris

Using ufsdump and ufsrestore

HI Gurus, I have a sunfire V445 server running SAP ECC 6.0 with an Oracle database on Solaris 9 (SunOS 5.9). I recently completed a ufsdump to tape of the following files:- /, /usr, /oracle, /export, /sapr3, I want to restore these files from tape onto a different server of the same... (5 Replies)
Discussion started by: charleywasharo
5 Replies

3. Filesystems, Disks and Memory

Building New server using Ufsdump/ufsrestore

Hi Guys, Marry X-MAX in advance :) I would like to build a new server using ufsdump/ufsrestore. Both the servers are identical hardware and model. I am using Solaris 10 X86 O/S. I am having ufsdump "mydump.rootdump.gz" in a Central NFS server. What I did:- I took backup of root... (1 Reply)
Discussion started by: SanjayLinux
1 Replies

4. UNIX for Advanced & Expert Users

Building New server using ufsdump/ufsrestore

Hi Guys, Marry X-MAX in advance :) I would like to build a new server using ufsdump/ufsrestore. Both the servers are identical hardware and model. I am using Solaris 10 X86 O/S. I am having ufsdump "mydump.rootdump.gz" in a Central NFS server. What I did:- I took backup of root... (1 Reply)
Discussion started by: SanjayLinux
1 Replies

5. UNIX for Dummies Questions & Answers

nohup & mpiexec problems

Hi everyone - I'm trying to start a run of LAMMPS (which takes an input file) with mpiexec on multiple processors. I want to combine this with nohup so that I can log off the node. I've used the syntax below successfully on one cluster, but it doesn't work on the new one I'm using. Any... (0 Replies)
Discussion started by: erin85
0 Replies

6. Solaris

How to pipe ufsdump to ufsrestore?

Dear all, i want to copy the partition contents from a smaller disk to a larger disk but without modifying the target disk partition size. To this end, i tried to use piping ufsdump to ufsrestore as 'ufsdump 0f - /dev/dsk/c0t0d0s0 l ufsrestore -i - /dev/dsk/c0t1d0s0' but it was not successful. Can... (0 Replies)
Discussion started by: hadimotamedi
0 Replies

7. Solaris

How to pipe ufsdump to ufsrestore?

Dear all, i want to copy the partition contents from a smaller disk to a larger disk but without modifying the target disk partition size. To this end, i tried to use piping ufsdump to ufsrestore as 'ufsdump 0f - /dev/dsk/c0t0d0s0 l ufsrestore -i - /dev/dsk/c0t1d0s0' but it was not successful. Can... (6 Replies)
Discussion started by: hadimotamedi
6 Replies

8. Solaris

Using ufsrestore from a DAT tape of ufsdump backup

hi, was wondering if there is a problem with the patches, and if we wish to restore everything back to square one, how should we go about using ufsrestore from a DAT tape of ufsdump backup data ? (1 Reply)
Discussion started by: Exposure
1 Replies

9. Shell Programming and Scripting

echo & sed problems

I need a script to to instert the following line into my postfix master.cf file: flags=Rq user=filter argv=/etc/postfix/disclaimer -f ${sender} -- ${recipient}if I use echo I get the line truncated: :~ echo flags=Rq user=filter argv=/etc/postfix/disclaimer -f ${sender} -- ${recipient}... (3 Replies)
Discussion started by: barrydocks
3 Replies

10. UNIX for Advanced & Expert Users

SCO 6.0 & VMware problems

I've moved a physical server over to VMWare ESXi 5.1 using SCO 6.0 with MP4. For whatever reason, people are occasionally getting kicked out or are closing out their telnet session and it is leaving their processes running. When this happens, the sar %idle drops from 98-95% down to 25-20%. ... (1 Reply)
Discussion started by: Carlitos71
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 08:42 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy