search for: setperms

In a moment of epic stupidity, having ran out of space on the root partition of a server due to /var chewing up the space, I added a separate drive for the purpose of mounting it as /var To do so, I mounted the new drive as /var2, cp -R (in hindsight should had rsync to preserve attributes), deleted the original /var to free up space, edited fstab and rebooted... unsurprisingly to a fubar'd

On 04/05/2018 08:32 PM, Andrew Bartlett wrote: > On Sat, 2018-03-24 at 20:38 -0400, Ken McDonald via samba wrote: >>> By default, step 4 takes forever to run on large datasets because it >>> uses named entities. My ultimate plan was to use the numeric >>> user/group id's in that step instead of named ones so the Winbind cost >>> is not incurred. Seems for

On Sat, 2018-03-24 at 20:38 -0400, Ken McDonald via samba wrote: > > > By default, step 4 takes forever to run on large datasets because it > > uses named entities. My ultimate plan was to use the numeric > > user/group id's in that step instead of named ones so the Winbind cost > > is not incurred. Seems for the whole process, the calls to Winbind to > >

Basically, what I typed was: chown -R user2:user2 * chown -R user2:user2 .* chown -R user2:user2 *.* ...all in /home. Duh. I forgot which way recursive went. So, I then did: chown -R root:root * chown -R root:root .* chown -R root:root *.* ...this time in / to try and f things. Duh again. Other items need to have other owners & groups. So, how can I fix this? In MacOSX, there is a utility

Centos 4.3 Hi All: I just shot myself in the foot by change the owner/perms on the contents of the root directory (my bad!!!). I have done a quick compare with a running RHEL3U8 system and think I have every thing back to what it should be except for new directories media and selinux. Can someone out there currently running 4.3 send me an "ls -l" of their root directory so I can make

# HG changeset patch # User Rusty Russell <rusty@rustcorp.com.au> # Node ID b0de1894df67ac7c7d905bf61cdf0210b42752cc # Parent ba5d5bd28edf8bce89bdf9fc64047ee4f1dceded Xenstore watch rework Change watches to all fire simultaneously, removing priority argument. Watches no longer fired back to connection/domain which caused event. Fix up testsuite to match Use state enum, rather than return

Currently PVHVM Linux guests after ddacf5ef684a "xen/pv-on-hvm kexec: add xs_reset_watches to shutdown watches from old kernel" hang when run against oxenstored because it does not handle the unknown XS_RESET_WATCHES operation and does not reply. The symptom of this issue is a hang during boot at this point: cpu 1 spinlock event irq 70 CPU 1 irqstacks, hard=dec94000