Sent: Wednesday, October 29, 2008 9:48
PM
Subject: [Wireshark-users]
Wireshark/Dumpcap ignoring TMPDIR Environmentvariable
Hello,
In my environment
Wireshark/Dumpcap is ignoring the TMPDIR environment variable when creating
the temp files. I found some mention of TEMP environment variable so I
went ahead and set that just in case but no dice. Has anyone else seen
this on other platforms. I am seeing this problem with
both Wireshark 1.0.3 and 1.0.4, I have not tried moving to any earlier
versions. My servers are running MACOSX Leopard 10.5.5. I would
like to narrow down if this is a Wireshark issue or a Leopard issue. I
did see some mention in the list of other issues with temporary files but nope
that referenced the TMPDIR environment variable. Any assistance would be
appreciated. See output below for more details.
I have other
servers that are running MACOSX 10.3.9 with Wireshark version 0.99.6 and it is
working perfectly.
Thanks,
Lisa
[user@host.local]:
->echo
$TMPDIR
/opt/MPA/var/log/voip-captures/.wireshark-tmp
[user@host.local]:
->echo
$TEMP
/opt/MPA/var/log/voip-captures/.wireshark-tmp
[user@host.local]:
->dumpcap -v
Dumpcap
1.0.3
Copyright
1998-2008 Gerald Combs <gerald@xxxxxxxxxxxxx> and
contributors.
This is free software; see the source for copying conditions.
There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
Compiled with GLib
2.16.6, with libpcap 0.9.8, with libz 1.2.3, without
POSIX
capabilities.
NOTE: this build doesn't support the "matches"
operator for Wireshark filter
syntax.
Running on Darwin
9.5.0 (MacOS 10.5.5), with libpcap version 0.9.8.
Built using gcc
4.0.1 (Apple Inc. build 5465).
[user@host.local]:
File:
/var/tmp/etherk1xVjUffZ8
Packets: 71 Packets dropped:
0
This communication is the property of Qwest
and may contain confidential or privileged information. Unauthorized use of
this communication is strictly prohibited and may be unlawful. If you have
received this communication in error, please immediately notify the sender by
reply e-mail and destroy all copies of the communication and any attachments.
_______________________________________________
Wireshark-users
mailing
list
Wireshark-users@xxxxxxxxxxxxx
https://wireshark.org/mailman/listinfo/wireshark-users