[ldm-users] umask and LDM

  • To: "ldm-users@xxxxxxxxxxxxxxxx" <ldm-users@xxxxxxxxxxxxxxxx>
  • Subject: [ldm-users] umask and LDM
  • From: "Mullenax, Robert R. (WFF-820.0)[PERATON INC]" <robert.r.mullenax@xxxxxxxx>
  • Date: Mon, 4 Nov 2024 13:21:45 +0000
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=nasa.gov; dmarc=pass action=none header.from=nasa.gov; dkim=pass header.d=nasa.gov; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=OJ6WS+E9qE3T4QoaOfSvGZsIefFmI9dgyoaksL865q8=; b=nSURrJ/Q94PUxBZ5svDW5P8tV0e/uffeb3GJZ36NC2EJVsZHgHCOC2eDUUUiDBdJHMLYnImhDo5LwVKhKZWIp9qM1E2/1UeXD9pZUp7kMw3nTkuEFPSqXAAjF8DRN3+y73f1IXnUZ3rlrobjRcyguvZEOOwJdX4rXrFpLlL1kCjt/wONov8UGuTR1A2fjYFaakFHDLa+TZ/nW8FZSrY09os+rrUHQ4aBCngaag3Ls0YsNTvGb0cDicXZM4vxmzgffTAYipMqlDIcbgkjLYBA34EcO75BkeswPrA42eUdoD1FVKYvVWpM7RBigykGI8Oe6hCZ6rkurGpNhkpXwW0t6Q==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=DcGHCLrvyrANmxe3JjBsBe/cP8tT/0ooBYzKS7rlVWpySyv+qkxdN61bdzoTvWx9MEm0FZBTWY96TM/43KM6kuCu/v+M3NVieVuWV8OlqNVLdMVK8etkybGDw8uzwaafj2+FY1l1LuU77U/yX+eCYaDvEGde2SCEybLh6SaMVsYwLta4w2mLXiAevv0ZeA70QywNGa4hfO/hjb+07KSfk4OCF4Sm803YMUMQFQ4xmoMRCJ0QnsI1DVTgq/EoxUbRESSCa+z0A49kIVyIrAd/Eo11fXwukrV07zSPr3vByZCtl2sTJpblprauxeNGG5ULg2NpYgTquTmwQSOydJRKWA==
  • Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=nasa.gov;
Good morning,

I was wondering if anyone had seen this with LDM. I have umask set to 002 so as 
to have group write for the files/directories that are saved or created by LDM 
so that scripts can be run by another account in same groups as LDM. This has 
worked fine for many years, but all of the sudden I am having files/directories 
created without write permission for the group which is causing a script to 
fail. I am running RedHat 8 with ldm-6.13.16. In looking back, it looks like 
this started in July, I assume after some OS patch? Has anyone seen this?

Thanks,
Robert Mullenax



  • 2024 messages navigation, sorted by:
    1. Thread
    2. Subject
    3. Author
    4. Date
    5. ↑ Table Of Contents
  • Search the ldm-users archives: