[Nagiosplug-devel] Temporary file for plugins

[Patrick Proy]

I tried $TMPDIR on my linux, it was empty.... (rh 9.0)

In the release version on my scripts, I will put @localstatedir@ as base
directory, and for now "/tmp/" is OK.

Patrick 
nagios at proy.org

-----Message d'origine-----
De : nagiosplug-devel-admin at lists.sourceforge.net
[mailto:nagiosplug-devel-admin at lists.sourceforge.net] De la part de Andreas
Ericsson
Envoyé : mardi 30 novembre 2004 01:01
À : nagiosplug-devel at lists.sourceforge.net
Objet : Re: [Nagiosplug-devel] Temporary file for plugins

Patrick Proy wrote:
> Hi everybody,
> 
> I'm planning to update some of my snmp scripts and I really need to 
> store information - because of counter style variables of snmp -.
> I don't think a temporary file is a good solution (will there be a 
> /tmp on every system ? Can nagios user write in it ?), but I didn't 
> find anything else.
> 
> Will there be some kind of storage in Nagios 2.0 for the scripts ? 
> A temp directory directive ?
> 

The --sharedstatedir and --localstatedir directives will be available for
usage with the subst script (as @sharedstatedir@ and
@localstatedir@) and every posix-compliant system should have the $TMPDIR
environment variable set.

> Did someone find a good solution ?
> 
> Thanks for your answers,
> 
> Patrick Proy
> nagios at proy.org

-- 
Andreas Ericsson                   andreas.ericsson at op5.se
OP5 AB                             www.op5.se
Lead Developer


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide Read honest & candid reviews
on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________________
Nagios Plugin Development Mailing List
Nagiosplug-devel at lists.sourceforge.net
Unsubscribe at https://lists.sourceforge.net/lists/listinfo/nagiosplug-devel
::: Please include plugins version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null