From: Scott Taylor <scott@dctchambers.com>
To: linux-admin@vger.kernel.org
Subject: Re: counting shell args
Date: Mon, 16 Dec 2002 13:38:40 -0800 [thread overview]
Message-ID: <5.1.1.6.0.20021216132151.01c70450@mustang> (raw)
In-Reply-To: <Pine.LNX.4.33.0212161607130.25857-100000@router.windsormac hine.com>
At 01:12 PM 12/16/02, Mike Dresser wrote:
>On Mon, 16 Dec 2002, Scott Taylor wrote:
>
>The worst part about writing this backup script of mine was finding the
>return status from the previous pipe in the script.
>
>smbtar -s $pcname -x $share -p $password -u $username -t - -X /win95
>/win98 | gzip -1 > $filename.tar.gz
> if [ $PIPESTATUS -eq 0 ] && [ `ls -s $filename.tar.gz | awk
> '{print $1}'` -gt 25 ]; then
>
>$PIPESTATUS was hard to find.
That should be very useful to know. :)
Now you have me curious (grr...I just got over that) why do you care if
there are more than 25 blocks in your zipped file?
>All that because smbtar doesn't properly report errors, you have to
>check that it did in fact report a zero error return, AND verify it
>didn't just dump a 0 byte file cause the machine was unreachable.
quite painful.
>Even
>so, if the Windows PC crashes in the middle of the backup(happens enough
>to be annoying!), it'll still think the backup ran just fine, and dump a 0
>status back at you, making the backup incomplete.
Even better if the WinThing crashes on a Windows user that uses file names
like:
"This is my file that has numbers in it from last year end" on a set of
subdirectories that make the filename over 250 chars long.
Yes, I've seen that! LMAO Just try to recover that from your tar file. Ugly!
>Most odd. :D
Yes, the SMB/CIFS world is not a perfect world, but just look at what they
are trying to perfect. ;0)
Scott.
next prev parent reply other threads:[~2002-12-16 21:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-16 20:36 counting shell args Scott Taylor
2002-12-16 20:47 ` Mike Dresser
[not found] ` <Pine.LNX.4.33.0212161545230.25857-100000@router.windsormac hine.com>
2002-12-16 20:53 ` Scott Taylor
2002-12-16 20:57 ` Mike Dresser
[not found] ` <Pine.LNX.4.33.0212161555240.25857-100000@router.windsormac hine.com>
2002-12-16 21:05 ` Scott Taylor
2002-12-16 21:12 ` Mike Dresser
[not found] ` <Pine.LNX.4.33.0212161607130.25857-100000@router.windsormac hine.com>
2002-12-16 21:38 ` Scott Taylor [this message]
2002-12-16 21:49 ` Mike Dresser
[not found] ` <Pine.LNX.4.33.0212161645140.3389-100000@router.windsormach ine.com>
2002-12-16 22:18 ` Scott Taylor
2002-12-17 15:15 ` Mike Dresser
[not found] ` <Pine.LNX.4.33.0212171005410.13631-100000@router.windsormac hine.com>
2002-12-17 15:36 ` SysAdmin rants [was Re: counting shell args] Scott Taylor
2002-12-17 3:11 ` counting shell args dashielljt
[not found] ` <Pine.LNX.4.50.0212162211130.217-100000@athame.gmpexpress.n et>
2002-12-17 15:38 ` Scott Taylor
2002-12-18 4:13 ` dashielljt
-- strict thread matches above, loose matches on Subject: below --
2002-12-16 22:04 johnjulian1
2002-12-17 15:05 ` Mike Dresser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5.1.1.6.0.20021216132151.01c70450@mustang \
--to=scott@dctchambers.com \
--cc=linux-admin@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox