Re: Properties init: Could not determine current working directory. -- JAVA400-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: Properties init: Could not determine current working directory.
From: David Gibbs <david@xxxxxxxxxxxx>
Date: Fri, 9 Jan 2026 10:56:43 -0600
List-archive: <https://archive.midrange.com/java400-l/>
List-post: <mailto:java400-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/java400-l>, <mailto:java400-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/java400-l>, <mailto:java400-l-request@lists.midrange.com?subject=unsubscribe>

On Fri, Jan 9, 2026 at 10:40 AM Charles Wilt <charles.wilt@xxxxxxxxx> wrote:

does /home exist on DEV but not prod?

/home exists on both

Are the permissions the same?

Ah, no, they aren't.

The permissions for prod /home are 'drwxrwsr-x'.
The permissions for dev /home are 'drwxrwsrwx'.

Just thinking out loud, given that the i defaults to /home if /homes/cwilt

for instance doesn't exist.

Interesting theory ... I'll talk to our infra folks.

david

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Properties init: Could not determine current working directory. , Charles Wilt

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.