[Solved] Questions about /etc/group and /etc/gshadow

This morning, package filesystem was upgraded to 2015.02-1 and pacnew files were created for /etc/group and /etc/gshadow. I ran diff against my current files, and the differences seem very minor, to me. I need some guidance to understand whether I should implement the pacnew changes.
The only significant difference I see in the group file is that in my original version, my username is added to the wheel group. This seems correct, to me.
For gshadow, there is the same difference for wheel. However, there are several entries where my original entry contains an exclamation point, but the new version does not. For example:
< proc:!::
> proc:::
If I run man /etc/gshadow, it does not give me what I understand as a man page, and gives me what appears to be a listing of the stuff in my /etc/gshadow file, instead. Which does not help me.
So, like I say, I need some guidance on dealing with these pacnew files.
Tim
PS - I now see that "man gshadow" gives me an actual man page. Sorry. I am currently studying it.
Last edited by ratcheer (2015-02-24 21:37:52)

After the update to filesystem 2015.02-1 some voices in /etc/gshadow were changed (in the pacnew file) from
systemd-journal-gateway:!::
systemd-timesync:!::
systemd-network:!::
systemd-bus-proxy:!::
systemd-resolve:!::
to
systemd-journal-gateway:::
systemd-timesync:::
systemd-network:::
systemd-bus-proxy:::
systemd-resolve:::
What's the change? Before they had a locked password (the ! sign) and now they haven't?

Similar Messages

/etc/group and /etc/passwd corrupted

My /etc/group and /etc/passwd (and possibly others) are corrupted (my silly error handling pacnew files). I tried restoring the backups (group- and similar) and also ran grpconv, pwdconv,, pwck without fixing things. I've edited the files, using those in another machine as a template but no luck.
Various commands (e.g. ssh) fail with the message:
No user exists for uid 1000
Before I give up and reinstall, is there any way I can restore things to how they should be?

Thanks for replies. I can't recreate my user because it's already there. I can log in as ac without difficulty and do most things - just a few (mportant) fail.
I don't understand why it keeps saying the user ac is uid 1000. After reading the wikis I think my /etc/group and /etc/passwd are correct. /etc/passwd has:
ac:x:1000:100::/home/ac:/bin/bash
and /etc/group has:
users:x:100:ac
ac:x:100:ac
I'm not sure the last line should be there, but removing it doesn't help. The entries on a second machine are similar.
I'll sleep on it to see if I think of something else to try in the morning, otherwise I'll have to reinstall tomorrow.

Deleted my /etc/groups and /etc/gshadow and now no mouse and keyboard.

Hey.
So a few days ago I updated my system and did something we all know to avoid. I accidently moved the empty .pacnew files over my groups and gshadow files so my entire group layout is out of the window. I am an idiot I know. My mom told me that when I was six. So I am now looking at fixing my system. My biggest problem is that now xorg runs but the keyboard and mouse don't respownd. This isn't a USB problem since I tried using non USB keyboard. In runlevel 3 keyboard works fine.
Xorg.log says something about input bring used by someone else so my guess based on the above is that what I need to do is restore my old groups since its probably a group ownership problem. My question is if anyone knows which groups should I restore and how does one go about repairing the Damage? I would be thankfully to anyone who would take the time saving me from my own stupidity.
Last edited by Greenstuff (2012-08-22 08:03:26)

This might be the solution. Perhaps I should post my /etc/group file and you can fix yours? I don't know, did you ensure that all your groups have the correct GID?

[solved] Questions about pacman -Qk and -Qkk output.

I was looking through the pacman manual today to see if there was anything I could add to a some Arch maintenance scripts I've been working on and came across -Qk which, among other things, lists missing files. I ran pacman -Qk in terminal and found a few package installations were missing files. I reinstalled them manually check again and the files were no longer missing. The first package I saw that was missing a file was gnome-command-center for instance.
So I really have two questions.
1) Is it normal for packages to have missing files?
2) Is it a good idea to reinstall these packages to replace the missing files.
I then ran pacman -Qkk, and got even more disturbing information such as modification time mismatches and size mismatches.
$ pacman -Qkk |grep warning
warning: avahi: /etc/avahi/avahi-daemon.conf (Modification time mismatch)
warning: avahi: /etc/avahi/hosts (Modification time mismatch)
warning: avahi: /etc/avahi/services/sftp-ssh.service (Modification time mismatch)
warning: avahi: /etc/avahi/services/ssh.service (Modification time mismatch)
warning: avahi: /usr/lib/avahi/service-types.db (Modification time mismatch)
warning: avahi: /usr/share/avahi/service-types (Modification time mismatch)
warning: bash: /etc/bash.bash_logout (Modification time mismatch)
warning: bash: /etc/bash.bashrc (Modification time mismatch)
warning: bash: /etc/skel/.bash_logout (Modification time mismatch)
warning: bash: /etc/skel/.bash_profile (Modification time mismatch)
warning: bash: /etc/skel/.bashrc (Modification time mismatch)
warning: bluez: /etc/bluetooth/main.conf (Modification time mismatch)
warning: bluez: /etc/dbus-1/system.d/bluetooth.conf (Modification time mismatch)
warning: ca-certificates-java: /etc/default/cacerts (Modification time mismatch)
warning: cdrtools: /etc/default/cdrecord (Modification time mismatch)
warning: cdrtools: /etc/default/rscsi (Modification time mismatch)
warning: chromium: /etc/chromium/default (Modification time mismatch)
warning: chromium: /etc/chromium/default (Size mismatch)
warning: colord: /var/lib/colord (UID mismatch)
warning: colord: /var/lib/colord (GID mismatch)
warning: dhcpcd: /etc/dhcpcd.conf (Modification time mismatch)
warning: e2fsprogs: /etc/mke2fs.conf (Modification time mismatch)
warning: filesystem: /etc/crypttab (Modification time mismatch)
warning: filesystem: /etc/fstab (Modification time mismatch)
warning: filesystem: /etc/fstab (Size mismatch)
warning: filesystem: /etc/group (Modification time mismatch)
warning: filesystem: /etc/group (Size mismatch)
warning: filesystem: /etc/gshadow (Permissions mismatch)
warning: filesystem: /etc/gshadow (Modification time mismatch)
warning: filesystem: /etc/gshadow (Size mismatch)
warning: filesystem: /etc/host.conf (Modification time mismatch)
warning: filesystem: /etc/hosts (Modification time mismatch)
warning: filesystem: /etc/issue (Modification time mismatch)
warning: filesystem: /etc/ld.so.conf (Modification time mismatch)
warning: filesystem: /etc/motd (Modification time mismatch)
warning: filesystem: /etc/mtab (Modification time mismatch)
warning: filesystem: /etc/mtab (Symlink path mismatch)
warning: filesystem: /etc/nsswitch.conf (Modification time mismatch)
warning: filesystem: /etc/passwd (Modification time mismatch)
warning: filesystem: /etc/passwd (Size mismatch)
warning: filesystem: /etc/profile (Modification time mismatch)
warning: filesystem: /etc/resolv.conf (Modification time mismatch)
warning: filesystem: /etc/resolv.conf (Size mismatch)
warning: filesystem: /etc/securetty (Modification time mismatch)
warning: filesystem: /etc/shadow (Permissions mismatch)
warning: filesystem: /etc/shadow (Modification time mismatch)
warning: filesystem: /etc/shadow (Size mismatch)
warning: filesystem: /etc/shells (Modification time mismatch)
warning: flashplugin: /etc/adobe/mms.cfg (Modification time mismatch)
warning: flashplugin: /etc/adobe/mms.cfg (Size mismatch)
warning: glibc: /etc/locale.gen (Modification time mismatch)
warning: glibc: /etc/locale.gen (Size mismatch)
warning: gnome-control-center: /usr/share/polkit-1/rules.d/gnome-control-center.rules (Permission denied)
warning: gnomenu: /usr/share/cairo-dock/plug-ins/Dbus/third-party/GnoMenu/GnoMenu (Modification time mismatch)
warning: gnomenu: /usr/share/cairo-dock/plug-ins/Dbus/third-party/GnoMenu/GnoMenu (Size mismatch)
warning: gnomenu: /usr/share/cairo-dock/plug-ins/Dbus/third-party/GnoMenu/GnoMenu.conf (Modification time mismatch)
warning: gnomenu: /usr/share/cairo-dock/plug-ins/Dbus/third-party/GnoMenu/GnoMenu.conf (Size mismatch)
warning: gnomenu: /usr/share/cairo-dock/plug-ins/Dbus/third-party/GnoMenu/auto-load.conf (Permissions mismatch)
warning: gnomenu: /usr/share/cairo-dock/plug-ins/Dbus/third-party/GnoMenu/auto-load.conf (Modification time mismatch)
warning: gnomenu: /usr/share/cairo-dock/plug-ins/Dbus/third-party/GnoMenu/auto-load.conf (Size mismatch)
warning: gnomenu: /usr/share/cairo-dock/plug-ins/Dbus/third-party/GnoMenu/icon (Modification time mismatch)
warning: gnomenu: /usr/share/cairo-dock/plug-ins/Dbus/third-party/GnoMenu/icon (Size mismatch)
warning: gnomenu: /usr/share/cairo-dock/plug-ins/Dbus/third-party/GnoMenu/preview (Permissions mismatch)
warning: gnomenu: /usr/share/cairo-dock/plug-ins/Dbus/third-party/GnoMenu/preview (Modification time mismatch)
warning: gnomenu: /usr/share/cairo-dock/plug-ins/Dbus/third-party/GnoMenu/preview (Size mismatch)
warning: grub: /boot/grub/grub.cfg (Permissions mismatch)
warning: grub: /boot/grub/grub.cfg (Modification time mismatch)
warning: grub: /boot/grub/grub.cfg (Size mismatch)
warning: iproute2: /etc/iproute2/ematch_map (Modification time mismatch)
warning: iproute2: /etc/iproute2/rt_dsfield (Modification time mismatch)
warning: iproute2: /etc/iproute2/rt_protos (Modification time mismatch)
warning: iproute2: /etc/iproute2/rt_realms (Modification time mismatch)
warning: iproute2: /etc/iproute2/rt_scopes (Modification time mismatch)
warning: iproute2: /etc/iproute2/rt_tables (Modification time mismatch)
warning: jack: /etc/security/limits.d/99-audio.conf (Modification time mismatch)
warning: java-common: /etc/profile.d/jre.csh (Modification time mismatch)
warning: java-common: /etc/profile.d/jre.sh (Modification time mismatch)
warning: jre7-openjdk-headless: /etc/java-7-openjdk/calendars.properties (Modification time mismatch)
warning: jre7-openjdk-headless: /etc/java-7-openjdk/content-types.properties (Modification time mismatch)
warning: jre7-openjdk-headless: /etc/java-7-openjdk/flavormap.properties (Modification time mismatch)
warning: jre7-openjdk-headless: /etc/java-7-openjdk/fontconfig.bfc (Modification time mismatch)
warning: jre7-openjdk-headless: /etc/java-7-openjdk/fontconfig.properties (Modification time mismatch)
warning: jre7-openjdk-headless: /etc/java-7-openjdk/logging.properties (Modification time mismatch)
warning: jre7-openjdk-headless: /etc/java-7-openjdk/net.properties (Modification time mismatch)
warning: jre7-openjdk-headless: /etc/java-7-openjdk/psfont.properties.ja (Modification time mismatch)
warning: jre7-openjdk-headless: /etc/java-7-openjdk/psfontj2d.properties (Modification time mismatch)
warning: jre7-openjdk-headless: /etc/java-7-openjdk/sound.properties (Modification time mismatch)
warning: jre7-openjdk-headless: /etc/java-7-openjdk/tz.properties (Modification time mismatch)
warning: jre7-openjdk-headless: /etc/java-7-openjdk/amd64/jvm.cfg (Modification time mismatch)
warning: jre7-openjdk-headless: /etc/java-7-openjdk/images/cursors/cursors.properties (Modification time mismatch)
warning: jre7-openjdk-headless: /etc/java-7-openjdk/management/jmxremote.access (Modification time mismatch)
warning: jre7-openjdk-headless: /etc/java-7-openjdk/management/jmxremote.password (Modification time mismatch)
warning: jre7-openjdk-headless: /etc/java-7-openjdk/management/management.properties (Modification time mismatch)
warning: jre7-openjdk-headless: /etc/java-7-openjdk/management/snmp.acl (Modification time mismatch)
warning: jre7-openjdk-headless: /etc/java-7-openjdk/security/java.policy (Modification time mismatch)
warning: jre7-openjdk-headless: /etc/java-7-openjdk/security/java.security (Modification time mismatch)
warning: jre7-openjdk-headless: /etc/java-7-openjdk/security/nss.cfg (Modification time mismatch)
warning: krb5: /etc/krb5.conf (Modification time mismatch)
warning: krb5: /var/lib/krb5kdc/kdc.conf (Modification time mismatch)
warning: libcups: /etc/cups/client.conf (Modification time mismatch)
warning: libirman: /etc/irman.conf (Modification time mismatch)
warning: libnl: /etc/libnl/classid (Modification time mismatch)
warning: libnl: /etc/libnl/pktloc (Modification time mismatch)
warning: libreoffice-still-common: /etc/libreoffice/bootstraprc (Modification time mismatch)
warning: libreoffice-still-common: /etc/libreoffice/psprint.conf (Modification time mismatch)
warning: libreoffice-still-common: /etc/libreoffice/sofficerc (Modification time mismatch)
warning: libreoffice-still-common: /etc/profile.d/libreoffice-still-common.csh (Modification time mismatch)
warning: libreoffice-still-common: /etc/profile.d/libreoffice-still-common.sh (Modification time mismatch)
warning: linux: /etc/mkinitcpio.d/linux.preset (Modification time mismatch)
warning: linux: /usr/lib/modules/3.16.2-1-ARCH/modules.alias (Modification time mismatch)
warning: linux: /usr/lib/modules/3.16.2-1-ARCH/modules.alias (Size mismatch)
warning: linux: /usr/lib/modules/3.16.2-1-ARCH/modules.alias.bin (Modification time mismatch)
warning: linux: /usr/lib/modules/3.16.2-1-ARCH/modules.alias.bin (Size mismatch)
warning: linux: /usr/lib/modules/3.16.2-1-ARCH/modules.builtin.bin (Modification time mismatch)
warning: linux: /usr/lib/modules/3.16.2-1-ARCH/modules.dep (Modification time mismatch)
warning: linux: /usr/lib/modules/3.16.2-1-ARCH/modules.dep (Size mismatch)
warning: linux: /usr/lib/modules/3.16.2-1-ARCH/modules.dep.bin (Modification time mismatch)
warning: linux: /usr/lib/modules/3.16.2-1-ARCH/modules.dep.bin (Size mismatch)
warning: linux: /usr/lib/modules/3.16.2-1-ARCH/modules.devname (Modification time mismatch)
warning: linux: /usr/lib/modules/3.16.2-1-ARCH/modules.softdep (Modification time mismatch)
warning: linux: /usr/lib/modules/3.16.2-1-ARCH/modules.symbols (Modification time mismatch)
warning: linux: /usr/lib/modules/3.16.2-1-ARCH/modules.symbols (Size mismatch)
warning: linux: /usr/lib/modules/3.16.2-1-ARCH/modules.symbols.bin (Modification time mismatch)
warning: linux: /usr/lib/modules/3.16.2-1-ARCH/modules.symbols.bin (Size mismatch)
warning: lirc-utils: /etc/lirc/lirc_options.conf (Modification time mismatch)
warning: lirc-utils: /etc/lirc/lircd.conf (Modification time mismatch)
warning: lirc-utils: /etc/lirc/lircmd.conf (Modification time mismatch)
warning: lvm2: /etc/lvm/lvm.conf (Modification time mismatch)
warning: mdadm: /etc/mdadm.conf (Modification time mismatch)
warning: mime-types: /etc/mime.types (Modification time mismatch)
warning: mkinitcpio: /etc/mkinitcpio.conf (Modification time mismatch)
warning: mkinitcpio: /etc/mkinitcpio.conf (Size mismatch)
warning: mplayer: /etc/mplayer/codecs.conf (Modification time mismatch)
warning: mplayer: /etc/mplayer/input.conf (Modification time mismatch)
warning: nano: /etc/nanorc (Modification time mismatch)
warning: networkmanager: /etc/NetworkManager/NetworkManager.conf (Modification time mismatch)
warning: openresolv: /etc/resolvconf.conf (Modification time mismatch)
warning: openssl: /etc/ssl/openssl.cnf (Modification time mismatch)
warning: pacman: /etc/makepkg.conf (Modification time mismatch)
warning: pacman: /etc/makepkg.conf (Size mismatch)
warning: pacman: /etc/pacman.conf (Modification time mismatch)
warning: pacman: /etc/pacman.conf (Size mismatch)
warning: pacman-mirrorlist: /etc/pacman.d/mirrorlist (UID mismatch)
warning: pacman-mirrorlist: /etc/pacman.d/mirrorlist (GID mismatch)
warning: pacman-mirrorlist: /etc/pacman.d/mirrorlist (Modification time mismatch)
warning: pacman-mirrorlist: /etc/pacman.d/mirrorlist (Size mismatch)
warning: pam: /etc/environment (Modification time mismatch)
warning: pam: /etc/default/passwd (Modification time mismatch)
warning: pam: /etc/security/access.conf (Modification time mismatch)
warning: pam: /etc/security/group.conf (Modification time mismatch)
warning: pam: /etc/security/limits.conf (Modification time mismatch)
warning: pam: /etc/security/namespace.conf (Modification time mismatch)
warning: pam: /etc/security/namespace.init (Modification time mismatch)
warning: pam: /etc/security/pam_env.conf (Modification time mismatch)
warning: pam: /etc/security/time.conf (Modification time mismatch)
warning: polkit: /etc/polkit-1/rules.d/50-default.rules (Permission denied)
warning: pulseaudio-alsa: /etc/asound.conf (Modification time mismatch)
warning: rhash: /etc/rhashrc (Modification time mismatch)
warning: rhash: /etc/rhashrc (Size mismatch)
warning: rsync: /etc/rsyncd.conf (Modification time mismatch)
warning: rsync: /etc/xinetd.d/rsync (Modification time mismatch)
warning: samba: /etc/conf.d/samba (Modification time mismatch)
warning: samba: /etc/logrotate.d/samba (Modification time mismatch)
warning: samba: /etc/pam.d/samba (Modification time mismatch)
warning: sudo: /etc/sudoers (Modification time mismatch)
warning: sudo: /etc/sudoers (Size mismatch)
warning: systemd: /etc/dbus-1/system.d/org.freedesktop.hostname1.conf (Modification time mismatch)
warning: systemd: /etc/dbus-1/system.d/org.freedesktop.locale1.conf (Modification time mismatch)
warning: systemd: /etc/dbus-1/system.d/org.freedesktop.login1.conf (Modification time mismatch)
warning: systemd: /etc/dbus-1/system.d/org.freedesktop.machine1.conf (Modification time mismatch)
warning: systemd: /etc/dbus-1/system.d/org.freedesktop.systemd1.conf (Modification time mismatch)
warning: systemd: /etc/dbus-1/system.d/org.freedesktop.timedate1.conf (Modification time mismatch)
warning: systemd: /etc/pam.d/systemd-user (Modification time mismatch)
warning: systemd: /etc/systemd/bootchart.conf (Modification time mismatch)
warning: systemd: /etc/systemd/coredump.conf (Modification time mismatch)
warning: systemd: /etc/systemd/journald.conf (Modification time mismatch)
warning: systemd: /etc/systemd/logind.conf (Modification time mismatch)
warning: systemd: /etc/systemd/resolved.conf (Modification time mismatch)
warning: systemd: /etc/systemd/system.conf (Modification time mismatch)
warning: systemd: /etc/systemd/timesyncd.conf (Modification time mismatch)
warning: systemd: /etc/systemd/timesyncd.conf (Size mismatch)
warning: systemd: /etc/systemd/user.conf (Modification time mismatch)
warning: systemd: /etc/udev/udev.conf (Modification time mismatch)
warning: systemd: /var/log/journal/remote (GID mismatch)
warning: texlive-core: /etc/texmf/web2c/updmap.cfg (Modification time mismatch)
warning: texlive-core: /etc/texmf/web2c/updmap.cfg (Size mismatch)
warning: util-linux: /etc/pam.d/chfn (Modification time mismatch)
warning: util-linux: /etc/pam.d/chsh (Modification time mismatch)
warning: util-linux: /etc/pam.d/login (Modification time mismatch)
warning: util-linux: /etc/pam.d/su (Modification time mismatch)
warning: util-linux: /etc/pam.d/su-l (Modification time mismatch)
warning: vim-runtime: /etc/vimrc (Modification time mismatch)
warning: vlc: /usr/lib/vlc/plugins/plugins.dat (Modification time mismatch)
warning: vlc: /usr/lib/vlc/plugins/plugins.dat (Size mismatch)
warning: xorg-xinit: /etc/X11/xinit/xinitrc (Modification time mismatch)
warning: xorg-xinit: /etc/X11/xinit/xserverrc (Modification time mismatch)
warning: xorg-xinit: /etc/skel/.xinitrc (Modification time mismatch)
warning: xorg-xinit: /etc/skel/.xsession (Modification time mismatch)
warning: xorg-xinit: /etc/skel/.xsession (Size mismatch)
warning: yaourt: /etc/yaourtrc (Modification time mismatch)
I'm assuming all of those are bad. "Warning" rarely sounds friendly, though for those files I've modified myself, such as passwd, shadow, and group, its okay. I assume I can fix msot of these by running # pacman -S {package}?
Last edited by nstgc (2014-09-14 01:26:04)

Awk processes the output from pacman, splits it using [white]space[⁣s] as delimiter and prints only first field $1, which is the package name. Those reoccur if several files are involved, so just to be sure, I also used awks sort, maybe that could be skipped or alternatively sort command outside awk used instead. This sorted output gets fed into uniq, which outputs only unique strings coming from input. And that leaves you with the package list.
Edit: I think those are whitespaces actually, which if I recall correctly include space.
Edit2: So this might be better and certainly a little faster:
pacman -S $(pacman -Qkq | awk '{print $1}' | uniq)
# And this should be even faster, since the output pacman
# delivers seems to be sorted anyway. Should you parse
# something else, use my first suggestion instead.
pacman -Qkq | awk 'BEGIN{ y=0; }; {x=$1; if (x == y){ next; }; print $1; y=x;}'
Edit3: Out of curiosity I tested different methods measuring execution time with a input file consisting out of 1443 lines from pacman -Qkkq. Here are the results and the bottom is the test script.
Sun 14 Sep 15:14:26 CEST 2014, Generating input file
Sun 14 Sep 15:15:22 CEST 2014, Loops: 10
0 : /tmp/awk-adv.log
0.01 : /tmp/awk-sort.log
0 : /tmp/awk-sort-outside.log
0.002 : /tmp/awk-uniq.log
Seconds: 0
Sun 14 Sep 15:15:22 CEST 2014, Loops: 20
0.001 : /tmp/awk-adv.log
0.0095 : /tmp/awk-sort.log
0.0005 : /tmp/awk-sort-outside.log
0 : /tmp/awk-uniq.log
Seconds: 1
Sun 14 Sep 15:15:23 CEST 2014, Loops: 50
0 : /tmp/awk-adv.log
0.0096 : /tmp/awk-sort.log
0.0002 : /tmp/awk-sort-outside.log
0 : /tmp/awk-uniq.log
Seconds: 2
Sun 14 Sep 15:15:25 CEST 2014, Loops: 100
0.0003 : /tmp/awk-adv.log
0.0092 : /tmp/awk-sort.log
0 : /tmp/awk-sort-outside.log
0.0003 : /tmp/awk-uniq.log
Seconds: 5
Sun 14 Sep 15:15:30 CEST 2014, Loops: 200
0.00045 : /tmp/awk-adv.log
0.00955 : /tmp/awk-sort.log
0.0001 : /tmp/awk-sort-outside.log
0.0006 : /tmp/awk-uniq.log
Seconds: 8
Sun 14 Sep 15:15:38 CEST 2014, Loops: 500
0.00042 : /tmp/awk-adv.log
0.0094 : /tmp/awk-sort.log
0.0004 : /tmp/awk-sort-outside.log
0.00026 : /tmp/awk-uniq.log
Seconds: 21
Sun 14 Sep 15:15:59 CEST 2014, Loops: 1000
0.00034 : /tmp/awk-adv.log
0.00942 : /tmp/awk-sort.log
0.00042 : /tmp/awk-sort-outside.log
0.00025 : /tmp/awk-uniq.log
Seconds: 42
Sun 14 Sep 15:16:41 CEST 2014, Loops: 2000
0.00038 : /tmp/awk-adv.log
0.009355 : /tmp/awk-sort.log
0.000285 : /tmp/awk-sort-outside.log
0.00042 : /tmp/awk-uniq.log
Seconds: 83
Sun 14 Sep 15:18:04 CEST 2014, Loops: 5000
0.000388 : /tmp/awk-adv.log
0.009274 : /tmp/awk-sort.log
0.00034 : /tmp/awk-sort-outside.log
0.000366 : /tmp/awk-uniq.log
Seconds: 208
Sun 14 Sep 15:21:32 CEST 2014, Loops: 10000
0.00036 : /tmp/awk-adv.log
0.009286 : /tmp/awk-sort.log
0.000346 : /tmp/awk-sort-outside.log
0.000358 : /tmp/awk-uniq.log
Seconds: 419
Sun 14 Sep 15:28:31 CEST 2014, Loops: 20000
0.00029 : /tmp/awk-adv.log
0.009115 : /tmp/awk-sort.log
0.0002725 : /tmp/awk-sort-outside.log
0.000299 : /tmp/awk-uniq.log
Seconds: 828
Sun 14 Sep 15:42:19 CEST 2014, Loops: 50000
0.0003174 : /tmp/awk-adv.log
0.0093014 : /tmp/awk-sort.log
0.0002422 : /tmp/awk-sort-outside.log
0.000292 : /tmp/awk-uniq.log
Seconds: 2171
The awk internal sorting is the slowest method, but it seems it initializes longer, since there appears to be a constant difference between internal and external sorting. Uniq fed by awk is faster with smaller loops, but gets slower if repeated more often, yet overall remain fastest with the unique function I used within awk. It appears the more lines the input has, the slower uniq in comparison uniq in awk gets. Here is the testing script:
#!/bin/bash
LOOPS=('10' '20' '50' '100' '200' '500' '1000' '2000' '5000' '10000' '20000' '50000');
rm /tmp/results*.log
echo $(date), Generating input file;
pacman -Qkkq > /tmp/input.txt
for LOOP in ${LOOPS[@]}; do
START=$(date +%s);
echo $(date), Loops: $LOOP;
for i in $(seq $LOOP); do env TIME='%e:%U:%S' time awk '{print $1 | "sort" }' /tmp/input.txt | uniq; done 2>&1 >/dev/null | grep : > /tmp/awk-sort.log
for i in $(seq $LOOP); do env TIME='%e:%U:%S' time awk '{print $1}' /tmp/input.txt | sort | uniq; done 2>&1 >/dev/null | grep : > /tmp/awk-sort-outside.log
for i in $(seq $LOOP); do env TIME='%e:%U:%S' time awk '{print $1}' /tmp/input.txt | uniq; done 2>&1 >/dev/null | grep : > /tmp/awk-uniq.log
for i in $(seq $LOOP); do env TIME='%e:%U:%S' time awk 'BEGIN{ y=0; }; {x=$1; if (x == y){ next; }; print $1; y=x;}' /tmp/input.txt; done 2>&1 >/dev/null | grep : > /tmp/awk-adv.log
for FILE in /tmp/awk-*.log; do awk 'BEGIN{x=0; y=0; FS=":"}; {x++; y=y+$1;}; END{print "\t"y/x"\t:\t"FILENAME;}' "$FILE"; done | sort >> /tmp/results-sorted.log
for FILE in /tmp/awk-*.log; do awk 'BEGIN{x=0; y=0; FS=":"}; {x++; y=y+$1;}; END{print "\t"y/x"\t:\t"FILENAME;}' "$FILE"; done | tee -a /tmp/results.log
END=$(date +%s);
DIFF=$(( $END - $START ));
echo Seconds: $DIFF;
done | tee /tmp/awk.log
Last edited by emeres (2014-09-14 14:38:18)

[SOLVED] Question about package updates and ABS

Hello,
I have manually compile my kernel in order to apply a patch my laptop needs to suspend. So I use abs and customize the pkgbuild. A few days ago when the update for kernel26-2.6.33.3-2 came out, I thought I'd just refresh abs, rebuild, and then I'd be up to date. But instead now pacman -Syu tells me that there is still an update for the kernel.
Does building from ABS not get you the latest package update?
Also, what exactly is the package update compared to a software update? I'm guessing that it is an arch only update to the package but the software itself is the same version. Or am I totally off?
Thanks for the help!
Last edited by Fingel (2010-05-12 03:42:38)

When building via ABS, the package installed gets its version from the PKGBUILD ($pkgver-$pkgrel). Pacman just looks at available version vs installed version to tell if you should upgrade.
Your abs tree was probably just not up to date; just because pacman -Syu says your mirror has a package, doesn't mean building via abs _at that moment_ will get that version.
Be sure to run `abs` to update your tree, then when you're editing the PKGBUILD, check which version it's building. In some cases, you can simply increment those numbers right in the PKGBUILD before building as source files are often fetched based on those variables, etc. -- but I don't know if I'd recommend that when building something like the kernel.
Last edited by brisbin33 (2010-05-11 17:08:12)

[SOLVED] Question about DM's and WM's

ok, so, i am not really a newbie, but im sure this is a newbie question. so im trying to run window manager's such as MetaCity and BlackBox, and i would like to also run a Display Manager, such as GDM (Gnome Display Manager) which is the one i normally use. i know that adding
# ...Or add any other Display Manager you want here.
exec metacity
to .xinitrc will make it start up, but i think that Display Managers may bypass the .xinitrc, though i may be wrong. i have a few Window Managers installed, but none of them are listed in GDM, only actual Desktop Environments. I have no clue what to do with this, but i do know that i want to have a window manager show up in my display manager, so that i can lock my computer if need be. i know a lot of people just simply use a Window Manager and dont bother with a Display Manager, but i would like to use one. any information or links to a wiki page i may have not found yet would be appreciated, thanks!
Last edited by SpidermanD5 (2014-12-27 00:15:43)

SpidermanD5 wrote:... but i think that Display Managers may bypass the .xinitrc
Some do, some don't.
SpidermanD5 wrote:any information or links to a wiki page i may have not found yet would be appreciated, thanks!
What have you found? Each DM should have a wiki page, and probably a man page. That's how you'd find out how to configure them as they are all different.

[SOLVED]Questions about openbsd ffs and linux ext2fs

Hello everyone.
First of all, forgive me if the post is not on the correct section.
I'm going to install arch linux to my thinkpad and i have some questions:
I have two external hard disks (once) formatted to openbsd ffs. (now i'm making efforts to turn it to ext2fs )
1) Does Arch have by default read support for openbsd ffs filesystems or i have to build a custom kernel?
2)I would mostly like to have read and write access from both OSs. I know that ext2fs should work for read and write from Openbsd and Linux so this could be a good option. My problem starts when i try it for example to format the disks under Openbsd; i successfully created a working ext2 partition, but when i try it
with an Ubuntu live cd to see if it works, i see no partitions and i have to reformat it. On the other hand, if i create it under Linux, then it's not working under Openbsd.
So now that i'm migrating to arch, which are the good practices to make partitions work/cooperate under both OSs?
notes: On Linux, i tried with both gparted and disk utility with no luck.( It works for linux but not for OpenBSD).
Has anyone managed to work with both ext2fs and both Linux Openbsd?
What are the best practices in such cases?
Last edited by lambda (2012-09-26 12:07:26)

well fstype is one thing , bsd labels vs mbr is another. In case with linux and bsd dualboot best practice is vfat (aka fat32) but with all its limitations ( i can be wrong here 'cos i never tested dual zfs for instance ).

[SOLVED] Question about URxvt - fontconfig and ulr launching

So today I am slightly rewriting my .Xdefaults (actually outright copying MrElendig's...), and now my URxvt won't launch...
Here is what I get as an output:
[ ~ ] urxvt
urxvt: unable to load base fontset, please specify a valid one using -fn, aborting.
What's the error?
You can find my .Xdefaults here:
http://pastie.org/231515
Also, I have an issue with my URL handling from within URxvt:
I want to launch a URL clicking on it. But no matter what I specify for urxvt*matcher.Button, I can only use my middle mouse button (on a Thinkpad X60s.... could that be the problem?).
Last edited by Stalafin (2008-07-11 14:14:54)

pseup wrote:
Xft is for prettier, anti aliased / hinted fonts I think. But I find that using xft makes urxvt extremely sluggish when using large terminals.
Eg, I open a full screen URXVT (1920x1200), running 'time seq -s " " 1 100000' to print out heaps of text:
0m0.306s with '-*-terminus-*-*-*-*-12-*-*-*-*-*-*-*'
0m12.165s with 'xft:terminus:pixelsize=12'
Sure I'm not looking at full screen terminals of scrolling text all the time, but it is still noticeably slow even in small terminals.
I don't have url matching enabled now, but I did use Gigamo's config at one stage to try it, and the mouse behaved as expected. Not sure if there is anything in it that would make a difference: http://github.com/gigamo/config/tree/master/.Xdefaults
pseup: I get different results. urxvt -fn xft:terminus:pixelsize=12 gives me a time of 5.351s and urxvt -fn -*-terminus-*-*-*-*-12-*-*-*-*-*-*-* gives me a time of ranges from 4-9 seconds! This is in a half screen terminal with the other terminal running the urxvt -fn *** command.
Fullscreen terminal (1280x800) with fonts defined in Xdefaults give the same results you got. intresting.
Last edited by semperfiguy (2008-07-10 18:10:04)

[SOLVED] /etc/group or /etc/gshadow are inconsistent, grpck shows " ".

After updating, pacman said
==> Warning: /etc/group or /etc/gshadow are inconsistent.
but when running grpck there was no output.
I would guess this means everything is OK. Is this the case?
In case it matters, these are my /etc/group and /etc/gshadow.
Last edited by trusktr (2013-09-06 07:46:30)

Check these:
https://bbs.archlinux.org/viewtopic.php?id=131484
https://bbs.archlinux.org/viewtopic.php?pid=1064456

[SOLVED] Today's update of /etc/group, /etc/passwd and /etc/gshadow

Hello,
During the regular updates I received an update of /etc/groups. I wonder what I should do here, as there are some differences between the old file and the pacnew one. I suppose that when I use the command to add my user to a group, it gets written into this file. So, just recklessly moving the pacnew file in the place of the old one, will mess up all my groups, won't it?
Then what should I do? All the entries in the pacnew file are also present in the old one, so I guess I could just delete the pacnew one and keep the old one. Am I right?
EDIT: The same goes to /etc/passwd and /etc/gshadow.
Last edited by Unia (2012-10-06 09:51:23)

teateawhy wrote:
If you had the uuid user before like me the uuid line in your own files is different from the pacnew file. You have to delete the uuid line near the bottom in your old file. Then insert the new uuid entry including the new number in the place near the top suggested by the pacnew file. Keep the other lines untouched, then save your changes and delete the pacnew files.
Edit: On a system that has actually been modified from a default install the new files will for sure be different to the old ones.
Thanks, teateawhy! I currently have this listed in /etc/passwd:
uuidd:x:998:998::/:/sbin/nologin
And this is in the .pacnew file:
uuidd:x:68:68:uuidd:/:/sbin/nologin
So, I can just copy the entry from the .pacnew file, overwriting the old entry, right?
What I don't understand is how the two numbers 998 representing the UID and GID can suddenly change to 68. Shouldn't they have to correspond with some other reference or list of users/groups...?
I'm sure it's fine to just replace the entry as you suggested, but I wondered if there was a way to double-check which uid/gid should be used? It's not that I don't trust you, but I don't fully understand how these group/passwd files work and I'm trying to get my head round it all.
Cheers,
esuhl

[SOLVED] /etc/passwd and /etc/shadow -- pwck shows missing groups

I recently found out about the pwck and grpck commands to check for errors/inconsistencies in the passwd, group, shadow and gshadow files... grpck returns no errors, but pwck returns this:
user 'avahi': no group 84
user 'postgres': no group 88
user 'ntp': no group 87
pwck: no changes
These are the relevant lines from /etc/passwd:
avahi:x:84:84:Avahi daemon:/:/bin/false
postgres:x:88:88:PostgreSQL user:/var/lib/postgres:/bin/bash
ntp:x:87:87:Network Time Protocol:/var/lib/ntp:/bin/false
There are lines for those users in /etc/shadow... but... I'm not sure what I need to do to fix the problem.
I think I understand enough, now, to maintain the files in future, but would anyone know I can fix this?
Last edited by esuhl (2012-10-08 20:22:05)

2ManyDogs wrote:I don't know how to fix the errors, but I'm really curious about why you decided to run those commands. Were you having a problem you thought might be ralated to groups and/or passwords? What are groups 84, 97, and 88?
Ha! Well... when I started using Arch I really didn't know much about Linux and I an update providing some .pacnew files (/etc/group, gshadow, passwd, shadow) and... well... I don't know what I did, but I think it was probably not what I should have done(!). I used grpck in the past and got no errors and it suddenly occurred to me today that there should be an equivalent for checking /etc/passwd... so that's why I just ran the commands now. Everything seems to be working, however...
I don't have an entry for groups 84, 87 and 88 in my /etc/group file... Hmmm...
I tried running this command to find any files associated with that group, but only get the following:
[root@i7pc tim]# find / -gid 88
find: `/run/user/1000/gvfs': Permission denied
find: `/proc/1806/task/1806/fd/5': No such file or directory
find: `/proc/1806/task/1806/fdinfo/5': No such file or directory
find: `/proc/1806/fd/5': No such file or directory
find: `/proc/1806/fdinfo/5': No such file or directory
I get similar output for the other groups, so... can I just delete them from /etc/passwd and /etc/shadow?
I notice I have the avahi package installed, however, and group 84 relates to user 'avahi'... so... surely I need the avahi user...?
Last edited by esuhl (2012-10-07 23:09:30)

Login Process & Security of /etc/passwd and /etc/shadow

Guys,
I have few questions, Please help me out.
1. What is the Solaris 8 and Solaris 9 environment's boot files ?
2. While Logging into Solaris Operating Environment , which is file is responsible for Login Process ? Through which file/command the username and password is cross checked with /etc/passwd and /etc/shadow ?
3. We all know that /etc/passwd come with -rw-r--r-- permission and /etc/shadow comes with -r--------. I did a chmod and assigned 000 to both the files. But Still I am able to change the password for the normal user. And as a root I am still able to cat the contents of both the files.
Help me understand these concepts.
Thank you.
Arut

Sounds like you're very new to Solaris:
1. What is the Solaris 8 and Solaris 9 environment's boot files ?/kernel/genunix is the primary boot file. The directory structure in /kernel is also boot related. /usr/kernel is also boot related.
2. While Logging into Solaris Operating Environment , which is file is responsible for Login Process ? Through which file/command the username and password is cross checked with /etc/passwd and /etc/shadow ?Generally three files are related: /etc/passwd, /etc/shadow, and the program /bin/login. Some applications will process /etc/passwd and /etc/shadow on their own and bypass /bin/login - but for you're purposes this is a good general answer.
As a minor example (and if I remember correctly), say someone uses telnet to log into a system. Telnet prompts for the login ID. Once input, it passes forks off /bin/login with the login ID. /bin/login reads the user password information from /etc/shadow and takes the first two bytes from the password field (column 2 using : as field seperator) which is the crypt salt (see crypt man page). /bin/login prompts for the password which the user inputs. /bin/login takes the user input password and the salt value read from /etc/shadow for that user and pushes it through crypt. It then takes the resultant crypt output and compares it against what it read from /etc/shadow - if they matches the user has input the right password. If not, it prompts the user again with a password prompt.
3. We all know that /etc/passwd come with -rw-r--r-- permission and /etc/shadow comes with -r--------. I did a chmod and assigned 000 to both the files. But Still I am able to change the password for the normal user. And as a root I am still able to cat the contents of both the files.To change your password you run the passwd command. That command is SUID root - so for a short period of time you become root within the context of that process. Root is basically god mode and doesn't care about file access priviledges generally. So that fact that /etc/passwd and /etc/shadow have 000 file access permissions doesn't matter - root can still read and write to them.

A few questions about the ka790gx and dka790gx

i have a few questions about the ka790gx and dka790gx , how much better is the dka790gx compaired to the ka790gx ? . how much difference does the ACC function make to overclocking etc , i plan on getting a phenom II 940BE or 720BE . i already have the ka790gx so would it be worth building another system using the dka790gx mobo , or should i keep what i already have and just change the cpu ?

It's largely irrelevant what other boards had VRM issues other than the KA790GX - the fact is it died at stock settings. Since there is little cost difference between the more robust DKA790GX (or Platinum if you really need 1394) why bother with the proven weakling? There are other examples around of the KA not having a robust power section. There's no way I would use even a 95W TDP CPU in the KA and absolutely not O/C.....!
As for the credentials of Custom PC, I have generally found their reviews accurate and balanced, and echo my own findings where applicable. If a little too infrequent.
The fact that the KA has such a huge VRM heatsink leads me to my other comments on the Forum, particularly regarding the "fudge" aspect:
"""Henry is spot on - the notion that adding a heatsink to the top of the D2PAK or whatever MOSFETS is effective is virtually worthless. The device's die thermal junction is the tab on the device back - which is always against the PCB pad. The majority of heat is therefore dissipated in to the board, and the fact that the epoxy plastic encapsulation gets hot is simply due to the inability of the heat to be conducted away from the device die via the tab. Not sure when Epoxy become an effective conductor of heat.... Good practice is to increase the size of the PCB pad (or "land" in American) such that the enlarged PCB copper area acts as an adequate heatsink. This is still not as effective as clamping a power device tab to an actual piece of ali or copper, but since the devices used are SMD devices, this is not possible. However, the surface area required to provide sufficient PCB copper area to act as a heatsink for several devices isn't available in the current motherboard layouts. Where industrial SBC designs differ in this respect is to place the VRM MOSFETs on the back of the PCB on very enlarged PCB pads - where real estate for components is not an issue.
Gigabyte's UD3 2oz copper mainboards sound like a good idea, on the face of it. However, without knowing how they have connected the device tabs to where and what remains a mystery. I suspect it is more hype than solution, although there will be some positive effect. From an electrical perspective, having lower resistance connecting whatever to whatever (probably just a 0V plane) is no bad thing.
The way the likes of ASUS sort of get round the problem is to increase the sheer number of MOSFET devices and effectively spread the heat dissipation over a larger physical area. This works to a degree, there is the same amount of heat being dissipated, but over several more square inches. The other advantage of this is that each leg of the VRM circuit passes less current and therefore localised heat is reduced. Remember that as well as absolute peak operating temperature causing reduced component life, thermal cycling stresses the mechanical aspects of components (die wire bonds for example) as well as the solder joints on the board. Keeping components at a relatively constant temperature, even if this is high (but within operating temperature limits), is a means of promoting longevity.
For myself, the first thing I do with a seperate VRM heatsink is take it off and use a quiet fan to blow air on to the VRM area of the PCB - this is where the heat is. This has the added benefit of actively cooling the inductors and capacitors too....
Cooling the epoxy component body is a fudge. If the epoxy (and thus any heatsink plonked on top of it) is running at 60C, the component die is way above that.....
It's better than nothing, but only just."""

Question about Everyone Group in SharePoint 2013

Hi,
I have couple of question about EVERYONE group below,
         - As per the best practice which Group we should use instead of EVERYONE group in Sharepoint ?
         - What is the difference between Everyone and All Authenticated Users Group
We have added Everyone Group in different sites, now the question is if we hide this group showing up in sharepoint people picker, is there any impact interms of current site?
         - Is there any way we can hide Everyone group showing up in the people picker only for the site / Site Collection level.
Please help.
Thanks
srabon

There is no functional difference between the Everyone group and All Authenticated Users (after Active Directory has been upgraded to Server 2003 native schema).
I'm not aware of any function to hide the group from the People Picker.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Question About Color's and Gradients

Hi all,
I have a question about color swatches and gradients.
I am curious to know, if I have 2 color swatches that I make into a gradient color, is it posible to change the tint of each indivdual color in that gradient and have that applied to the gradient without having to adjust the gradients opacity.
The reason that I'm asking this is because in creating a project I found that the colors that I chose for to make my gradient from my swatches were to dark, and while I can adjust each one's tint to my liking (if the object they were applied to was going to be a solid color) but that doesn't seem to apply to the overall gradient.
I hope that makes sense, I know that this was something that was able to be accomplished in quark and was wondering if I can do something similar.

If you double click your gradient swatch (after adding it to the swatches)
Then click a colour stop in the gradient, and then change the drop down menu to CMYK (or rgb)
And you can alter the percentages there. It's not much use for spot colours but it's a start.
But making tint swatches would be a good start anyway.
At least then when you double click the gradient (in the swatches) to edit it you can choose from CMYK, RGB, LAB, or Swatches and adjust each colour stop to your liking.

[Solved] Questions about /etc/group and /etc/gshadow

Similar Messages

Maybe you are looking for