similar to: CentOS default accounts in /etc/passwd

dear all, i have two server, smb1 act as PDC Debian 3.1 Samba 3.0.14a-Debian OpenLDAP 2.3.32 smb2 act as fileserver auth to PDC via winbindd FC3 Samba 3.0.24 the problems are : i can get the groups and users when running getent passwd and getent group from smb1. but i just can get the groups when running getent group or wbinfo -g from smb2. if i run getent passwd or wbinfo -u from smb2, it

Hello! I just noticed a behavior of samba I am wundering about: I have a Samba-Server with a [homes] section. As user "barth" I conect to this using \\<Samba-Server>\<any username> permission is checked for "barth" with his password and access is granted with the rights of barth to the HOME-directory of <any username>. So far so good. This also works

I did not understand the man pages for sudo and incorrectly interpreted the results. I interpreted the ALL to apply to all commands defined in the sudoers file. Basically, I'm an idiot, but here is the chain I followed, and the correct interpretation. In the man pages on sudo, it says the following: A User_List is made up of one or more usernames, uids (prefixed with

Hi, I have a CyberPower UPS connected to a Ubuntu karmic machine. All functions are working well. I can use upsc to see all the UPS parameters, power loss and battery low events are correctly detected, and shutdown is correctly initiated. If I run upsdrvctl shutdown, the UPS cuts power immediately. However, if I simulate a shutdown with upsmon -c fsd, the UPS fails to cut power. The

Greetings! I have successfully installed and configured nut package. All i want now is to power off ups. If i run upsmon -c fsd as root - everything goes fine, system and ups gracefully shutting down. If i unplug power cable from an ups, then system is down, but ups still on load. Any help would be appreciated. Debian Lenny x86 ups.conf [ippon] driver = megatec port = /dev/ttyS0

Two enhancements of the type "zone" would be great: - a zone transition from ''running'' to ''installed'' should do a complete shutdown of the zone before ''zoneadm -z <zonename> halt'' is called, respectively instead of it. zlogin <zonename> "init 0" does the job, but it comes back immediately without checking

Hi all I have a simple setup: Ubuntu 9.04 server APC Back-UPS ES-700 connected with USB nut installed from packages (apt-get install nut). I guess that makes it version 2.4.1 ? The problem: When issuing: upsmon -c fsd I get a messages that the server will halt, and it does. But it won't restart again. I have set the BIOS to always power on, and this works fine when if I just cut the

Hi, I was trying to hack the /etc/rc.d/init.d/halt script under RH 9.0 in a way to achieve a clean shutdown: - commanding the RAID arrays to readonly mode - turning off my hardware watchdog, ... etc. See details below. At the end of all this preparation, and very close to the last lines of the halt script, I would then issue: 1. /usr/bin/belkinunv -x wait /dev/ttyS0 2. (OR, with a smart ups:

Fairly straightforward code motion in system.h into the sub-arch layer. Affected functionality include control register accessors, which are virtualizable but with great overhead due to the #GP cost; wbinvd, and most importantly, halt and interrupt control, which is non-virtualizable. Since read_cr4_safe can never fault on a VMI kernel (P5+ processor is required for VMI), we can omit the fault

Fairly straightforward code motion in system.h into the sub-arch layer. Affected functionality include control register accessors, which are virtualizable but with great overhead due to the #GP cost; wbinvd, and most importantly, halt and interrupt control, which is non-virtualizable. Since read_cr4_safe can never fault on a VMI kernel (P5+ processor is required for VMI), we can omit the fault

Hello all. Thank you for reading. I'm hoping someone can point me in the right direction here. I am looking to implement a wrapper script/utility that will prompt for a ticket number before running certain commands. I've used similar scripts in the past on systems that I didn't have admin access. The wrapper would do something like this: [root at vm-helios-019] shutdown -h now

I have 4 machines at home: 1 Linux Centos 4.4 running as a PDC 1 Linux Centos domain member running as my file server. Winbind works properly and I'm able to share files perfectly well 1 Windows XP sp2, member of my domain. No problem accessing files on Centos domain member 1 Linux Fedora Core 5, also a domain member. I'm unable to logon my Fedora 5 machine to my domain. I've joined

Folks - With Dovecot 1.0.7, we're seemingly unable to authenticate users for out-going SMTP access who are not residing directly within the main system passwd/shadow files. (I.e. the users seeded within our non-system "dovecot" userdbs & passwd files have no "smtp-auth" joy! (Ye olde "Relaying denied. Proper authentication required") I've mucked around

> I'm quite sure that in original Berkeley Unix, as on the VAX 11/780, halt > was an immediate halt of the CPU without any process cleanup or file system > umounting or anything. Early SunOS (pre-Solaris) was like this, too. > The SunOS 4.1.2 man page for halt says NAME halt - stop the processor SYNOPSIS /usr/etc/halt [ -oqy ] DESCRIPTION halt writes

Hi Charles, On Wednesday, July 13, 2016 11:40:09 PM Charles Lepple wrote: > On Jul 12, 2016, at 5:27 PM, Ivan Adzhubey <iadzhubey at rics.bwh.harvard.edu> > wrote: > > I have recently installed NUT 2.7.3.1 on a freshly installed Ubuntu 16.04 > > LTS (64-bit) system, connected via USB cable to APC Smart-UPS 1500 (SMT > > model). I am trying to make this configuration

On Sun, Jun 14, 2020 at 5:20 PM Pete Biggs <pete at biggs.org.uk> wrote: > > > fwiw, i've always used 'init 0' to shut down all sorts of unix/linux > > systems. > > In EL7/EL8, init is now a symlink as well because everything is > controlled by systemd. > > > On old school unix, and I think even early Linux, halt was an > > /immediate/

Working with different Linux Distributions makes the life harder. So far I have found out that 'poweroff' & 'reboot' has the same behaviour on Linux/Unix/BSDs. Best Regards, Strahil Nikolov ?? 15 ??? 2020 ?. 5:22:28 GMT+03:00, John Pierce <jhn.pierce at gmail.com> ??????: >On Sun, Jun 14, 2020 at 6:19 PM Pete Biggs <pete at biggs.org.uk> wrote: > >>

> fwiw, i've always used 'init 0' to shut down all sorts of unix/linux > systems. In EL7/EL8, init is now a symlink as well because everything is controlled by systemd. > On old school unix, and I think even early Linux, halt was an > /immediate/ halt, as in catch fire. might as well hit the power switch. > Not quite. Shutdown is a timed thing so you can tell it

On Sun, Jun 14, 2020 at 6:19 PM Pete Biggs <pete at biggs.org.uk> wrote: > > > I'm quite sure that in original Berkeley Unix, as on the VAX 11/780, halt > > was an immediate halt of the CPU without any process cleanup or file > system > > umounting or anything. Early SunOS (pre-Solaris) was like this, too. > > > The SunOS 4.1.2 man page for halt says

On Mon, Jul 13, 2015 at 10:21 AM, Jonathan Billings <billings at negate.org> wrote: > Are you saying that this is an interactive process on the system? I'd > suggest you make sure this isn't some sort of email ticket that stores > a password or emails it. > Thanks for the reply. I'm thinking that the password would only be there to confirm. It would not be stored