topic Re: Syscall already definied: lwp_mutex_unlock_2 in Operating System - HP-UX

Syscall already definied: lwp_mutex_unlock_2

Marco Queirolo — Mon, 04 Nov 2002 13:20:16 GMT

Hello,

After I installed some patch, the system can't boot. The next message show:
sysent_assign_function: syscall already definied
system call # 53
name is "lwp_mutex_unlock_2"
1 argument(s)
32-bit call function at 0x32da30
32-bit dynamic function at 0x32da30
64-bit call function at 0x2bf180
64-bit dynamic function at 0x0

when I tried to remove the bundle installed, the system shows a dependecy message dialiog, but is empty, and can't continue the uninstall.

Best regards.
Marco

Re: Syscall already definied: lwp_mutex_unlock_2

Dietmar Konermann — Mon, 04 Nov 2002 15:16:16 GMT

The old syscall number 53 is being reused after installing some HP-UX kernel patches.

The 53 was used at least by CA's software "eTrust Access Control". They are now using number 254 instead which is officially reserverd for them.

Maybe this helps: http://support.ca.com/Download/patches/etrust/access_control/QO22955.html.

Regards...
Dietmar.

Re: Syscall already definied: lwp_mutex_unlock_2

Stan Sieler — Wed, 04 Apr 2007 20:43:26 GMT

Dietmar said:

> The 53 was used at least by CA's
> software "eTrust Access Control". They are
> now using number 254 instead which is
> officially reserverd for them.

So, who do I talk to to reserve a system
call number? I need one, and am willing
to implement it in a manner where other
users/vendors can share access to it
(i.e., so that this isn't the start of
hundreds of users asking for one :)

BTW, HP-UX 10.20 has 254 as SYS_ULSDEST,
and HP-UX 11.11 doesn't mention 254,
and HP-UX 11.23 doesn't mention 254.

thanks,
Stan
sieler@allegro.com