Search Results

gzip certainly gives error when another process is writing to it.
Chain the next command with && i.e. only if successful.

find "$CAPDIR" -maxdepth 1 -type f |
awk -F/ '{print $NF}' |
while...

The way this is typically done during logrotation is to rename the logfile, then send a signal to the logging process to inform it that it needs to close its file descriptor and create a new logfile,...

If all it's doing is writing to the file, it should continue seamlessly. You can rename files in use and nothing happens as long as the inode, the file's unique ID on the filesystem, remains the...

ls /usr/bin/nslookup /usr/sbin/lsof /sbin/ifconfig /usr/sbin/dmidecode /sbin/ethtool /bin/netstat | wc -l
--ahamed

---------- Post updated at 08:49 PM ---------- Previous update was at 08:48 PM...

IMHO, regarding UIDs....

UIDs should never be retired, changed or reused.

If you work in any kind of environment that may persist over many years, or may audited you should never change or...

if your system is similiar below files (so like redhat variants) you can try to check these
# cat /etc/login.defs |grep -i id
# Directory where mailboxes reside, _or_ name of file, relative to...

sed '$d' infile > outfile
pword=$(tomcat-passwd $2)
echo ' <user username="'$1'" password="'$pword'" roles="'$3'" />' >> outfile
echo '</tomcat-users>' >> outfile

It has to do with how your shell expands the command.

Try this, assuming you're in the same directory as the file:

# mv ./-X ./dash-X


Then you can examine or remove the 'dash-X' file.