10 More Discussions You Might Find Interesting
1. OS X (Apple)
Mac users...
I updated this MBP from OSX 10.12.1 to the brand new OSX 10.12.2 two days ago.
A week ago I installed the Xcode suite.
Now the QT shell audio capture in another recent thread is broken when exporting a file.
It gives an error in a window, paraphrasing, The action is not... (4 Replies)
Discussion started by: wisecracker
4 Replies
2. Ubuntu
We are having a little problem on a server. We want that some users should be able to do e.g. sudo and become root, but with the restriction that the user can't change root password. That is, a guarantee that we still can login to that server and become root no matter of what the other users will... (2 Replies)
Discussion started by: 244an
2 Replies
3. SuSE
I access over 100 SUSE SLES servers as root from my admin server, via ssh sessions using ssh keys, so I don't have to enter a password. My SUSE Admin server is setup in the following manner:
1) Remote root access is turned off in the sshd_config file.
2) I am the only user of this admin... (6 Replies)
Discussion started by: dvbell
6 Replies
4. Shell Programming and Scripting
Currently in my system Red Hat is installed. And Many user connect to my machine via SSH Techia Terminal.
I want to give some users a root level access.
Can anyone please help me how to make it possible. I too searched on the Google but didn't find the correct way
Regards
ADI (4 Replies)
Discussion started by: adisky123
4 Replies
5. UNIX for Dummies Questions & Answers
hi
i am new to unix and i have abig task. i have to \run particular commands having root privileges from a non root user. i know sudo is one of the way but i need sum other approach kindly help
Thanks (5 Replies)
Discussion started by: suryashikha
5 Replies
6. AIX
Hello
I have a question.
I have a box with Aix 5.3 but I want to disable root access direct from any terminal or console. I mean If I want to login to 10.10.10.10
login:root
password *********
Root access is not permited
Which file I have to edit. to the users first login with... (4 Replies)
Discussion started by: lo-lp-kl
4 Replies
7. Solaris
Hi,
The security auditor give a this statement , what to do ?
On my solaris system (S10)
"The User ID "root" should not be used on the system - the su and
the priviledged account should be used from each administrator for
accountability purposes"
What to do ? (3 Replies)
Discussion started by: falcon16
3 Replies
8. Shell Programming and Scripting
Hi,
I just wanted to know to what files root does not have access, not even read....I read that .profile for any user is the only file which root cannot access is it true..??...If we have to use passwords and ID's in a script can we use them in .profile and call them as parameters..???
... (3 Replies)
Discussion started by: mgirinath
3 Replies
9. SCO
We have SCO 5.0.5 and can't log into system as "root". The system indicates the password is incorrect. No one knows what happened.
How can we resolve this issue.. Are there files we can restore from backup...?
Any suggestions would be appreciated.
Thank you.. (2 Replies)
Discussion started by: RBurer
2 Replies
10. Linux
wish to know how to access root password it root password is forgotten in linux (1 Reply)
Discussion started by: wojtyla
1 Replies
Dpkg::Vendor::Default(3) libdpkg-perl Dpkg::Vendor::Default(3)
NAME
Dpkg::Vendor::Default - default vendor object
DESCRIPTION
A vendor object is used to provide vendor specific behaviour in various places. This is the default object used in case there's none for
the current vendor or in case the vendor could not be identified (see Dpkg::Vendor documentation).
It provides some hooks that are called by various dpkg-* tools. If you need a new hook, please file a bug against dpkg-dev and explain
your need. Note that the hook API has no guaranty to be stable over an extended period. If you run an important distribution that makes use
of vendor hooks, you'd better submit them for integration so that we avoid breaking your code.
FUNCTIONS
$vendor_obj = Dpkg::Vendor::Default->new()
Creates the default vendor object. Can be inherited by all vendor objects if they don't need any specific initialization at object
creation time.
$vendor_obj->run_hook($id, @params)
Run the corresponding hook. The parameters are hook-specific. The supported hooks are:
before-source-build ($srcpkg)
The first parameter is a Dpkg::Source::Package object. The hook is called just before the execution of $srcpkg->build().
keyrings ()
The hook is called when dpkg-source is checking a signature on a source package. It takes no parameters, but returns a
(possibly empty) list of vendor-specific keyrings.
register-custom-fields ()
The hook is called in Dpkg::Control::Fields to register custom fields. You should return a list of arrays. Each array is an
operation to perform. The first item is the name of the operation and corresponds to a field_* function provided by
Dpkg::Control::Fields. The remaining fields are the parameters that are passed unchanged to the corresponding function.
Known operations are "register", "insert_after" and "insert_before".
post-process-changelog-entry ($fields)
The hook is called in Dpkg::Changelog to post-process a Dpkg::Changelog::Entry after it has been created and filled with the
appropriate values.
update-buildflags ($flags)
The hook is called in Dpkg::BuildFlags to allow the vendor to override the default values set for the various build flags.
$flags is a Dpkg::BuildFlags object.
1.16.15 2014-06-05 Dpkg::Vendor::Default(3)