10 More Discussions You Might Find Interesting
1. UNIX and Linux Applications
Hi Everyone,
We are trying to do a logrotate for "catalina.out" daily, So have used the "copytruncate" option in the logrotate configuration but ended up seeing there was a 0kb file touched with "catalina.out" and the other file with the current date(compressed) file created and seems the log is... (2 Replies)
Discussion started by: thiyagoo
2 Replies
2. Shell Programming and Scripting
Hello,
I have been working on script in which search and replace the multiple pattern.
1. update_params.sh read the multiple pattern from input file ParamMapping.txt(old_entry|New_entry) and passing this values one by one to change_text.sh
2. change_text.sh read... (0 Replies)
Discussion started by: ketanraut
0 Replies
3. Shell Programming and Scripting
hi
i have a file as in follwoing:
cat apple.txt
Apple is a fruit
But this fruit is costly
Now I used the sed command and i see output as in following
# sed 's/fruit/healthy &/' fruit.txt
Apple is a healthy fruit
But this healthy fruit is costly
#
sed works fine here. But... (2 Replies)
Discussion started by: Priya Amaresh
2 Replies
4. Shell Programming and Scripting
Hi, An application is transferring a file to linux system with same file name. As file is transferring with same name always file will be overwritten. In this case we want to know what times file was overwirtten like below.
Modify: 2014-05-12 00:52:01.000000000
Modify: 2014-05-12... (2 Replies)
Discussion started by: Satyak
2 Replies
5. Shell Programming and Scripting
I have a script, which runs through cronjob every night 9 PM. It is supposed to do following tasks --
1- Connect to ftp.testsite.com via user redtest
2- Fetch file red_bill.txt to my local server, where my script is residing.
3- Rename red_bill.txt to red_bill.V01.txt everyday on sftp server.... (4 Replies)
Discussion started by: solaris_1977
4 Replies
6. UNIX Desktop Questions & Answers
I have loads of files in different directories which I do miner changed on them and till now I have to create totally new directories for them, specially as I deal with a whole directory at once :wall::wall::wall::wall:
it creates such as mess really
e.g.
FILES="F1/*"
for X in $FILES
do... (2 Replies)
Discussion started by: A-V
2 Replies
7. Linux
Long story short, there was some sort of corruption with my ide and the script I was working on has been over written with nothing (the file is blank now). The IDE doesn't store a back up from what I know (I'm using notepadd++ in wine lol I know I know I'm addictted to the nppftp sidebar and geany... (1 Reply)
Discussion started by: noPermissions
1 Replies
8. Programming
Hi ,
i have two basic requirement on linux platform . I am using C language to do this .
1) copying one file to another (assuming i know their file descriptors)
2) Overwriting a file using it file descriptor .
Please guide.
regards
Aki (2 Replies)
Discussion started by: meet123321
2 Replies
9. Shell Programming and Scripting
Hi all,
In our webserver customer wants to see the latest 10 files arrived. So the names are hardcoded in webpage like :
filename_01.txt
filename_02.txt
....
....
filename_10.txt
where the filename_01.txt is the latest one (typically the output of ls -1t) in the /../webpage directory.... (2 Replies)
Discussion started by: sabyasm
2 Replies
10. UNIX for Dummies Questions & Answers
So I dont enounter things like:
gzip: /sometimename.gz already exists; do you wish to overwrite (y or n)?
Want to add it into a script and if there is a file aready there to just overwrite it, otherwise the script will hang unless there is manual intervention. (1 Reply)
Discussion started by: LordJezo
1 Replies
synclist(4) File Formats synclist(4)
NAME
synclist - list of files to be synchronized when changing from one boot environment to another
SYNOPSIS
/etc/lu/synclist
DESCRIPTION
The synclist file lists files that will be synchronized when you switch from one boot environment (BE) to another. The file is part of the
Live Upgrade feature of the Solaris Operating Environment. See live_upgrade(5) for an overview of the Live Upgrade software.
The synclist file consists of a list of entries, with two fields per entry. The first field is a pathname, the second a keyword. The key-
word can be one of OVERWRITE, APPEND, or PREPEND. The meanings of these keywords is described below. synclist accepts comments; a comment
is indicated by a hash mark (#) in the first character position on a line.
The way in which a file is updated is indicated by the keyword in the second field of its synclist entry. All of these operations occur
upon the first boot of a newly activated BE. The keywords have the following semantics:
OVERWRITE
Overwrite the contents of a file with the contents of the file of the same name on the previously booted BE. Both directories and files
can be specified for overwriting. If you specify a directory, every file in and beneath the listed directory is subject to being over-
written. (Whether an individual file or directory is overwritten depends on the outcome of the comparison of file versions, described
below.) Following an overwrite operation, a file on a new BE has the same date of creation, mode, and ownership as the file of the same
name on the previously booted BE.
APPEND
Append the contents of a file on the previously booted BE to the contents of the file of the same name on the new BE. Use of APPEND
allows for the possibility of duplicate entries in a file. You cannot use APPEND with directories. Following an append operation, a
file on a new BE will have a different modified date and time from the same file on the previously booted BE. The mode and ownership
will be the same between the two files.
PREPEND
Prepend the contents of a file on the previously booted BE to the contents of the file of the same name on the new BE. Use of PREPEND
allows for the possibility of duplicate entries in a file. You cannot use PREPEND with directories. Following a prepend operation, a
file on a new BE will have a different modified date and time from the same file on the previously booted BE. The mode and ownership
will be the same between the two files.
The second (keyword) field in a synclist entry can be empty, in which case the OVERWRITE action is assumed.
In deciding when to update a file on a newly activated BE, Live Upgrade uses an algorithm illustrated in the table below. In the table,
"old" refers to a BE relinquishing activated status; "new" refers to a newly activated BE. The "resulting state" occurs when the new BE is
first booted.
+------------------+--------------------+----------------------+
|State of File | State of File |Resulting State |
| | | |
|on Old BE | on New BE |on New BE |
+------------------+--------------------+----------------------+
|Unchanged | Unchanged |Not updated |
+------------------+--------------------+----------------------+
|Updated | Unchanged |Updated |
+------------------+--------------------+----------------------+
|Unchanged | Updated |Not updated |
+------------------+--------------------+----------------------+
|Updated | Updated |Conflict Indicated |
+------------------+--------------------+----------------------+
When a file is updated on both an old and new BE, as shown in the last row of the table above, Live Upgrade reports the conflict and allows
you to resolve it.
Modify the contents of synclist with caution. Adding certain files to synclist might render a BE unbootable. Also, be careful in using the
file-inclusion and -exclusion options in lucreate(1M) in conjunction with changes you might make in synclist. Again, you could render a
system unbootable or end up with different results from what you expected.
Switching BEs among different Solaris Operating Environment marketing releases (for example, from a Solaris 9 BE to a Solaris 2.6 BE)
requires care. This is especially true if you make any modifications to synclist. For example, consider that the last-active BE contains
Solaris 9 and you want to activate a BE that contains Solaris 2.6. In synclist in the Solaris 9 BE, you have added files that are present
in Solaris 9 that are not present in Solaris 2.6 or that are no longer compatible with Solaris 2.6. If you forced synchronization with the
luactivate(1M) -s option, the BE containing Solaris 2.6 might be synchronized with files that might not work under Solaris 2.6.
EXAMPLES
Example 1: Updating the passwd File
Consider the following scenario:
1. You create a BE, named first.
2. You create a new BE, named second, using first as the source.
3. You add a new user to first, thereby making an addition to the passwd file in first.
4. Using luactivate(1M), you activate second. At this point, Live Upgrade recognizes that the passwd file has been updated in first and
not in second.
5. When you boot second for the first time, Live Upgrade, directed by the keyword OVERWRITE in synclist, copies passwd from first to sec-
ond, overwriting the contents in the latter BE.
The result described above obtains with any of the files associated with the OVERWRITE keyword in synclist. If the reverse had occurred--
you edited passwd on second and left passwd in first untouched--Live Upgrade would not have modified passwd in second when that BE was
first booted.
Example 2: Updating the /var/log/syslog File
Consider the following scenario:
1. You create a BE, named first.
2. You create a new BE, named second, using first as the source.
3. Logging occurs, adding to the contents of /var/log/syslog in first.
4. Using luactivate(1M), you activate second. At this point, Live Upgrade recognizes that /var/log/syslog has been updated in first and
not in second.
5. When you boot second for the first time, Live Upgrade, directed by the keyword APPEND in synclist, appends the contents of
/var/log/syslog in first to the same file in second.
The result described above obtains with any of the files associated with the APPEND keyword in synclist. If the reverse had occurred--you
changed /var/log/syslog on second and left /var/log/syslog in first untouched--Live Upgrade would not have modified /var/log/syslog in sec-
ond when that BE was first booted.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWluu |
+-----------------------------+-----------------------------+
|Interface Stability |Evolving |
+-----------------------------+-----------------------------+
SEE ALSO
luactivate(1M), lucreate(1M), lumake(1M), attributes(5), live_upgrade(5)
SunOS 5.10 6 Aug 2003 synclist(4)