Sponsored Content
Full Discussion: Clearing Swapfiles?
Top Forums UNIX for Dummies Questions & Answers Clearing Swapfiles? Post 54496 by locustfurnace on Monday 16th of August 2004 07:21:01 PM
Old 08-16-2004
try the command for more info:

info coreutils

or for a specific entry
info swapon
or
info shred
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Clearing Mail Queue

Hello, I am trying to clear my mail queue with the following command: rm /var/spool/mqueue/* But when I do this I get this error: /bin/rm: Argument list too long. Can someone tell me what that error means and what I can do to correct it so I can clear my mail queue? Thanks (2 Replies)
Discussion started by: Chet
2 Replies

2. Programming

clearing control stack?

Hi, Can someone please explain how is the control stack cleared when we exit from a function?or who clears the rescords in the control stack? Thanks (1 Reply)
Discussion started by: naan
1 Replies

3. Programming

Clearing Data in an Array

How would I clear all data from an array? Here is what I'm doing: while (1) { if ((numbytes = recv(sock2, buf, 100, 0)) == -1) { perror("recv"); } printf("%s : %s", inet_ntoa(their_addr.sin_addr), buf); }buf still has extra data in it, so when I print it, things from previous data is put... (3 Replies)
Discussion started by: Octal
3 Replies

4. HP-UX

clearing history

HI, Can anybody tell me...what is a command for clearing command history in HP-UX machine. I tried 'history -c' but it is not applicable.... Thanks JAGDISH MACHHI (4 Replies)
Discussion started by: jagdish.machhi@
4 Replies

5. Programming

clearing breakpoints using dbx v 7.2.1

Im unsure of how to clear break points using dbx v7.2.1 Ive tried using delete linenumber of breakpoint however this does not seem to work. Could anyone point me in the correct direction ? regards (0 Replies)
Discussion started by: JamesGoh
0 Replies

6. Linux

clearing history

Is it possible to clear certain specific commands from history. I mean not clearing the entire history (history -c). You don't want anyone to see a particular command you executed. must not also show you have cleared history. Is it possible ? (2 Replies)
Discussion started by: nitin09
2 Replies

7. AIX

log_file_system clearing script

Hi i need a script to manage the mount point for any log location (/u01/dump/log/) i need a script which removes files older then x days but it should not remove file with extention *.log, *.ora etc then for remaing files it must search the huge files like *.txt and do fuser <filename> and... (0 Replies)
Discussion started by: javeedkaleem
0 Replies

8. Shell Programming and Scripting

BASH - Clearing value in a variable

anyone has any idae how do i clear the value in a variable in BASH? So far I come across "Clear-variable", however it can only clear a "Local" and "Global" variable. I'm trying to clear a self-declared variable. Anyone has any suggestions? (4 Replies)
Discussion started by: vinzping
4 Replies

9. AIX

clearing PVID

HI admins, I am not able to clear pvid .I am getting below error. chdev -l hdisk273 -a pv=clear Method error (/usr/lib/methods/chgdisk): 0514-047 Cannot access a device. pv The disk is from SAN. I can clear remove the disk using rmdev.But if i run cfgmgr , this disk apperas... (2 Replies)
Discussion started by: newaix
2 Replies

10. Shell Programming and Scripting

Clearing a environmental variable

i set a variable from the command line: export GANG="james,roy,martin" i can access this variable ($GANG) from a script. but each time i run the script, the variable keeps getting bigger. more info keeps getting added to it. Is there anyway i can make the $GANG variable contain the... (3 Replies)
Discussion started by: SkySmart
3 Replies
SHRED(1)							   User Commands							  SHRED(1)

NAME
shred - overwrite a file to hide its contents, and optionally delete it SYNOPSIS
shred [OPTIONS] FILE [...] DESCRIPTION
Overwrite the specified FILE(s) repeatedly, in order to make it harder for even very expensive hardware probing to recover the data. Mandatory arguments to long options are mandatory for short options too. -f, --force change permissions to allow writing if necessary -n, --iterations=N Overwrite N times instead of the default (25) --random-source=FILE get random bytes from FILE (default /dev/urandom) -s, --size=N shred this many bytes (suffixes like K, M, G accepted) -u, --remove truncate and remove file after overwriting -v, --verbose show progress -x, --exact do not round file sizes up to the next full block; this is the default for non-regular files -z, --zero add a final overwrite with zeros to hide shredding --help display this help and exit --version output version information and exit If FILE is -, shred standard output. Delete FILE(s) if --remove (-u) is specified. The default is not to remove the files because it is common to operate on device files like /dev/hda, and those files usually should not be removed. When operating on regular files, most people use the --remove option. CAUTION: Note that shred relies on a very important assumption: that the file system overwrites data in place. This is the traditional way to do things, but many modern file system designs do not satisfy this assumption. The following are examples of file systems on which shred is not effective, or is not guaranteed to be effective in all file system modes: * log-structured or journaled file systems, such as those supplied with AIX and Solaris (and JFS, ReiserFS, XFS, Ext3, etc.) * file systems that write redundant data and carry on even if some writes fail, such as RAID-based file systems * file systems that make snapshots, such as Network Appliance's NFS server * file systems that cache in temporary locations, such as NFS version 3 clients * compressed file systems In the case of ext3 file systems, the above disclaimer applies (and shred is thus of limited effectiveness) only in data=journal mode, which journals file data in addition to just metadata. In both the data=ordered (default) and data=writeback modes, shred works as usual. Ext3 journaling modes can be changed by adding the data=something option to the mount options for a particular file system in the /etc/fstab file, as documented in the mount man page (man mount). In addition, file system backups and remote mirrors may contain copies of the file that cannot be removed, and that will allow a shredded file to be recovered later. AUTHOR
Written by Colin Plumb. REPORTING BUGS
Report bugs to <bug-coreutils@gnu.org>. COPYRIGHT
Copyright (C) 2006 Free Software Foundation, Inc. This is free software. You may redistribute copies of it under the terms of the GNU General Public License <http://www.gnu.org/licenses/gpl.html>. There is NO WARRANTY, to the extent permitted by law. SEE ALSO
The full documentation for shred is maintained as a Texinfo manual. If the info and shred programs are properly installed at your site, the command info shred should give you access to the complete manual. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +--------------------+--------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +--------------------+--------------------+ |Availability | SUNWgnu-coreutils | +--------------------+--------------------+ |Interface Stability | Uncommitted | +--------------------+--------------------+ NOTES
Source for GNU coreutils is available on http://opensolaris.org. shred 6.7 December 2006 SHRED(1)
All times are GMT -4. The time now is 08:39 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy