12-15-2014
Notice that there was a Kerberos problem lately which was fixed by an efix. See
this link and similar links for more detail and make sure you update to the latest level.
You might want to forego the efix if you operate from an internal network. Denial-of-Service type attacks are typically massively parallel and therefore unlikely to take place inside the LAN, so that you could wait for a regular update. Deploying efixes is a nasty thing to do and you ahve to undeploy them before you can resume normal update routines.
I hope this helps.
bakunin
This User Gave Thanks to bakunin For This Post:
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Has anyone successfully authenticated unix users via Active Directory using
LDAP client on AIX v5.2 or v5.3?? ldapsearch from our unix box retrieves
info from AD but having trouble authenticating unix id when I logon - get a msg ': 3004-318 Error obtaining the user's password information'. Not... (0 Replies)
Discussion started by: DANNYC
0 Replies
2. AIX
In windows, there is a software that can help integrate some fixes or files into installtion media ( I think the software is called nLight or something). For example, if you want to include some SATA drivers into the installation CD of Windows XP you would: 1)get the Windows XP installation CDs. 2)... (1 Reply)
Discussion started by: Dardeer
1 Replies
3. AIX
I have a DUAL VIO ( IBM Virtual I/O ) setup on p 570.
Two Vio server ( VIOS ) and many LPAR clients.
VIO ( latest version + service pack + applied the fix ) and AIX 6.1 ML2
When both VIOs are running, and if I turn on a Client LPAR, the LPAR hangs at LED 25b3 for more than 1 hour then it... (2 Replies)
Discussion started by: filosophizer
2 Replies
4. AIX
Hi
In my vio server I have the below output
$ lsvopt | grep -i SAPSITGS
sapsitgs_cdrom TL12UP.iso 3182
In my vio client lpar I have the below output
root@sapsitgs:/ # lsdev -Cc cdromcd0 Available Virtual SCSI Optical Served by VIO Server
cd1... (1 Reply)
Discussion started by: newtoaixos
1 Replies
5. AIX
Hello,
I've set up email alerts on AIX Servers. so that i can get email notifications (via mail relay server) when ever there is abnormal behavior.
for example
1) my script monitors CPU/disk/memory etc... when it reaches high water ark, it will send an email alert.
2) disk usage alerts
3)... (5 Replies)
Discussion started by: System Admin 77
5 Replies
6. AIX
I have been able to configure on an AIX 5.2 ldap.cfg so service starts correctly.
but when I try to log on with a windows user after entering the password login hangs and get no response.
I have set it up on Aix 5.3 with no problem but in Aix 5.2 I have not been able to log in.
ldap.cfg... (1 Reply)
Discussion started by: laxtnog
1 Replies
7. AIX
I have joined an AIX 7.1 into a 2012 AD domain sucesfully.
I can get ouput from wbinfo -u but when I try to access a share I get the following error :
check_ntlm_password: Authentication for user -> FAILED with
error NT_STATUS_NO_SUCH_USER
I have found that I'm missing... (0 Replies)
Discussion started by: laxtnog
0 Replies
8. AIX
Hi folks,
How can i configure an AIX LDAP client to authenticate against an Linux Openldap server over TLS/SSL?
It works like a charm without TLS/SSL.
i would like to have SSL encrypted communication for ldap (secldapclntd) and ldapsearch etc. while accepting every kind of certificate/CA.... (6 Replies)
Discussion started by: paco699
6 Replies
9. Solaris
I have very limited knowledge on LDAP configuration and have been trying fix one issue, but unsuccessful.
The server, I am working on, is Solaris-10 zone. sudoers is configured on LDAP (its not on local server). I have access to login directly on server with root, but somehow sudo is not working... (9 Replies)
Discussion started by: solaris_1977
9 Replies
10. UNIX for Advanced & Expert Users
Hi everybody,
I have Power5 server with 4 internal hdisks each of 70Gb.
VIOS server was installed via Virtual I/O Server Image Repository on the HMC.
HMC release - 7.7.0
VIOS rootvg installed on 2 disk(these disks merged to one storage pool during VIOS install process),and 2 others hdisks... (2 Replies)
Discussion started by: Ravil Khalilov
2 Replies
LEARN ABOUT DEBIAN
fsvs-url-format
FSVS - URL format(5) fsvs FSVS - URL format(5)
NAME
Format of URLs -
FSVS can use more than one URL; the given URLs are overlaid according to their priority. FSVS can use more than one URL; the given URLs
are overlaid according to their priority.
For easier managing they get a name, and can optionally take a target revision.
Such an extended URL has the form
['name:'{name},]['target:'{t-rev},]['prio:'{prio},]URL
where URL is a standard URL known by subversion -- something like http://...., svn://... or svn+ssh://....
The arguments before the URL are optional and can be in any order; the URL must be last.
Example:
name:perl,prio:5,svn://...
or, using abbreviations,
N:perl,P:5,T:324,svn://...
Please mind that the full syntax is in lower case, whereas the abbreviations are capitalized!
Internally the : is looked for, and if the part before this character is a known keyword, it is used.
As soon as we find an unknown keyword we treat it as an URL, ie. stop processing.
The priority is in reverse numeric order - the lower the number, the higher the priority. (See url__current_has_precedence() )
Why a priority?
When we have to overlay several URLs, we have to know which URL takes precedence - in case the same entry is in more than one. (Which is
not recommended!)
Why a name?
We need a name, so that the user can say 'commit all outstanding
changes to the repository at URL x', without having to remember the full URL. After all, this URL should already be known, as there's a
list of URLs to update from.
You should only use alphanumeric characters and the underscore here; or, in other words, w or [a-zA-Z0-9_]. (Whitespace, comma and
semicolon get used as separators.)
What can I do with the target revision?
Using the target revision you can tell fsvs that it should use the given revision number as destination revision - so update would go
there, but not further. Please note that the given revision number overrides the -r parameter; this sets the destination for all URLs.
The default target is HEAD.
Note:
In subversion you can enter URL@revision - this syntax may be implemented in fsvs too. (But it has the problem, that as soon as you
have a @ in the URL, you must give the target revision every time!)
There's an additional internal number - why that?
This internal number is not for use by the user.
It is just used to have an unique identifier for an URL, without using the full string.
On my system the package names are on average 12.3 characters long (1024 packages with 12629 bytes, including newline):
COLUMNS=200 dpkg-query -l | cut -c5- | cut -f1 -d' ' | wc
So if we store an id of the url instead of the name, we have approx. 4 bytes per entry (length of strings of numbers from 1 to 1024).
Whereas using the needs name 12.3 characters, that's a difference of 8.3 per entry.
Multiplied with 150 000 entries we get about 1MB difference in filesize of the dir-file. Not really small ...
And using the whole URL would inflate that much more.
Currently we use about 92 bytes per entry. So we'd (unnecessarily) increase the size by about 10%.
That's why there's an url_t::internal_number.
Author
Generated automatically by Doxygen for fsvs from the source code.
Version trunk:2424 11 Mar 2010 FSVS - URL format(5)