Cp via NFS vs. scp yields unexpected difference Post: 302934248

9 More Discussions You Might Find Interesting

1. Solaris

NFS write error on host : Stale NFS file handle

:confused:Hi all When i see in the /var/adm/messages, i saw the following error unix: NFS write error on host : Stale NFS file handle. unix: (file handle: 45ca415 3e7 a0000 2c7f6 3ebfc25f a0000 2 3e49) It is using sunOS 5.7. Is anybody know what is this error? Is is related to any network...

2. Red Hat

Difference between sync & async in nfs

Hi All.... This is related to exporting a file system through nfs. Just wanted to understand the significance of sync/async in nfs. We give this entry in /etc/export file. What is the difference between these two. Any hep is appreciated. Regards, Amol.

3. UNIX for Advanced & Expert Users

scp/untar in parallel issue tar : Unexpected EOF in archive

Hi Guys, I am facing a strange issue while doing parallel (using & for background) scp/untar operation from my unix box to multiple unix boxes... I am getting tar : unexpected EOF in archive error the code is as follows.,,, for i in 10 do sh -c "scp <command> ; ssh tar -xf <tar> -C...

4. Shell Programming and Scripting

exec perl in expect script yields "invalid command"

I'm trying to execute something like this: exec perl -i -pe 's/\015/\012/g' '${file}' in my expect script and I get: error "invalid command name \"perl\". however, if I run perl -i -pe 's/\015/\012/g' "/Users/Shared/menu-items.txt" directly in my terminal, it runs fine. I'm an...

5. Red Hat

Difference in file sizes being copied by scp. HELP!

Hello All, I am transfering a gzipped file from LINUX to LINUX using scp -C comand. It is a nightly job, called by crontab. After copy finishes, the file sizes are different between source and destination. Say .gz file is 14782805941 bytes on source and 13496172544 bytes on destination. When I...

6. AIX

Difference between NFS and GPFS

Hello Gurus, Could you please help me out of the difference between GPFS and NFS. Thanks- P

7. Shell Programming and Scripting

awk output yields error: awk:can't open job_name (Autosys)

Good evening, Im newbie at unix specially with awk From an scheduler program called Autosys i want to extract some data reading an inputfile that comprises jobs names, then formating the output to columns for example 1. This is the inputfile: $ more MapaRep.txt ds_extra_nikira_usuarios...

8. Solaris

NFS write error on host xyz: Stale NFS file handle - Solaris 10

Oct 13 12:19:15 xyz nfs: NFS write error on host xyz: Stale NFS file handle. Oct 13 12:19:15 xyz nfs: (file handle: 68000000 1bc5492e 20000000 377c5e 1ce9395c 720a6203 40000000 bdfb0400) Oct 13 12:19:15 xyz nfs: NFS write error on host zyz: Stale NFS file handle. Oct 13 12:19:15 xyz nfs: ...

9. UNIX for Beginners Questions & Answers

Simple conditional yields too many responses

In this script: #!/bin/bash # bird read -p "Enter name of a bird " REPLY=$REPLY birdname="duck sparrow hawk" for i in $birdname do if ] then echo "Yes, that is a bird." else echo "That is not a bird." fi done I get...

LEARN ABOUT OPENSOLARIS

systemd-networkd.service

SYSTEMD-NETWORKD.SERVICE(8)				     systemd-networkd.service				       SYSTEMD-NETWORKD.SERVICE(8)

NAME

       systemd-networkd.service, systemd-networkd - Network manager

SYNOPSIS

       systemd-networkd.service

       /lib/systemd/systemd-networkd

DESCRIPTION

       systemd-networkd is a system service that manages networks. It detects and configures network devices as they appear, as well as creating
       virtual network devices.

       To configure low-level link settings independently of networks, see systemd.link(5).

       systemd-networkd will create network devices based on the configuration in systemd.netdev(5) files, respecting the [Match] sections in
       those files.

       systemd-networkd will manage network addresses and routes for any link for which it finds a .network file with an appropriate [Match]
       section, see systemd.network(5). For those links, it will flush existing network addresses and routes when bringing up the device. Any
       links not matched by one of the .network files will be ignored. It is also possible to explicitly tell systemd-networkd to ignore a link by
       using Unmanaged=yes option, see systemd.network(5).

       When systemd-networkd exits, it generally leaves existing network devices and configuration intact. This makes it possible to transition
       from the initrams and to restart the service without breaking connectivity. This also means that when configuration is updated and
       systemd-networkd is restarted, netdev interfaces for which configuration was removed will not be dropped, and may need to be cleaned up
       manually.

CONFIGURATION FILES

       The configuration files are read from the files located in the system network directory /lib/systemd/network, the volatile runtime network
       directory /run/systemd/network and the local administration network directory /etc/systemd/network.

       Networks are configured in .network files, see systemd.network(5), and virtual network devices are configured in .netdev files, see
       systemd.netdev(5).

SEE ALSO

       systemd(1), systemd.link(5), systemd.network(5), systemd.netdev(5), systemd-networkd-wait-online.service(8)

systemd 237													       SYSTEMD-NETWORKD.SERVICE(8)