RE: Dir for HTTP instance remains in www when deleting the HTTP instance via iNav

When you create an HTTP instance, the conf, htdocs, logs directories are created.
It only makes sense that when you delete an instance, these should be deleted.
The files are all related to the config of the instance.
Why would you want to keep the config files for the instance, if the instance is no longer needed?

Paul

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Brad Stone
Sent: Tuesday, May 25, 2021 12:14 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Dir for HTTP instance remains in www when deleting the HTTP instance via iNav

I agree... I wouldn't want it to read through my config and delete everything.

On Tue, May 25, 2021 at 11:12 AM Jon Paris <jon.paris@xxxxxxxxxxxxxx> wrote:

Personally I'd be really ticked if it wiped out the directory and its
content. The fact that I n longer want the server should never be
taken to mean I don't want the files.


Jon Paris

On May 25, 2021, at 11:58 AM, Steinmetz, Paul via MIDRANGE-L <

midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

When deleting an HTTP instance using IBM Nav for I, the dir and sub

directories and all their contents remain in www directory. Why is this?
They should be deleted.

Example.
HTTP instance guijalk was deleted.
Below remain.

guijwalk DIR
conf DIR
htdocs DIR
logs DIR

IBM response.
The behavior you describe is the normal behavior that has been in
place

since HTTP Server powered by Apache has been in place on the IBM i.
If you think this should be changed I recommend submitting an RFE with
your suggestion.

I submitted an RFE.

Any thoughts from the group?

Thank You
_____
Paul Steinmetz
IBM I Power9 Administrator

Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071

610-826-9117 Work
610-826-9188 Fax
610-349-0913 Cell
610-377-6012 Home


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription

related questions.

Help support midrange.com by shopping at amazon.com with our
affiliate

link: https://amazon.midrange.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
related questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com