Re: [gentoo-user] how to fix syslog-ng warning about escaped regexp
On Wed, 01 May 2019 13:33:32 -0400, Neil Bothwick wrote: > > [1 ] > On Wed, 01 May 2019 07:23:50 -0400, John Covici wrote: > > > > > Hi. Since my last update I get the following warning when syslog-ng > > > > runs: > > > > awk: cmd. line:130: warning: regexp escape sequence `\"' is not a > > > > known regexp operator > > > > > > > > I could find nothing at bgo or a google search, so I am wondering if > > > > anyone knows how to fix this problem? I am running version 3.20.1 > > > > and perl version 5.28.2. > > > > > > > > Thanks in advance for any suggestions. > > > > > > I was getting this from the makewhatis cron job in man. The solution > > > was to replace man, which is deprecated, with man-db. > > > > How would this help my problem as I am getting nothing from > > makewhatis? > > What program is producing the log entries? Or is it syslog-ng itself that > is doing so? It seems to be syslog-ng itself, although it says awk command line 130.I do have man rather than man-db, so I will replace and see if things improve. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una cov...@ccs.covici.com
Re: [gentoo-user] how to fix syslog-ng warning about escaped regexp
"Neil Bothwick" , 01.05.2019, 19:33: > On Wed, 01 May 2019 07:23:50 -0400, John Covici wrote: >> > > Hi. Since my last update I get the following warning when syslog-ng >> > > runs: >> > > awk: cmd. line:130: warning: regexp escape sequence `\"' is not a >> > > known regexp operator >> > > >> > > I could find nothing at bgo or a google search, so I am wondering if >> > > anyone knows how to fix this problem? I am running version 3.20.1 >> > > and perl version 5.28.2. >> > > >> > > Thanks in advance for any suggestions. >> > >> > I was getting this from the makewhatis cron job in man. The solution >> > was to replace man, which is deprecated, with man-db. >> >> How would this help my problem as I am getting nothing from >> makewhatis? > What program is producing the log entries? Or is it syslog-ng itself that > is doing so? Nope, the "faulty" program is /usr/sbin/makewhatis, line 363, where a " is escaped for awk, which the new awk 5 does not need. s.
[gentoo-user] Re: Libreoffice and copying web pages
On 2019-04-30, Dale wrote: > Howdy, > > As some know, I got a printer. Now I'm trying to get some info and > print it using LOo for the most part. This is the way I do this. I go > to a web page, sites will vary, and I highlight what I want and copy it > to the clipboard. I then go to LOo and paste it as HTML, since that is > what it is. At that point, LOo fetches things like pics and such to > place on the document. It takes a little time and I avoid copying > videos since it can't print a video. For the most part, this works > great. It takes a minute or so to fetch the pics and such and > everything looks fine. I remove anything I don't want such as ads and > such. Basically, it looks like the web page but I can edit it to make > fonts larger etc. However, sometimes it doesn't work. > > When it doesn't work, this is usually what happens. I paste the > document and LOo gets very slow or doesn't respond at all. Sometimes it > gets to the point I have to literally kill the thing to get it to stop. > On the occasions that it is just slow, scrolling up or down to make > edits is very slow. I'm talking I move the mouse wheel and a minute or > two later it scrolls up a couple lines. In a document that is several > pages long, it takes forever to scroll to the top after pasting it in. > In older versions of LOo it didn't have this problem. It would copy and > paste and even while fetching the pics, it would respond very well and > was pretty fast. The pics sometimes would show up as empty boxes tho > until they were fetched. I would wait until that was done before saving > the docs. About a year or so ago, it started this very slow to > downright won't respond thing. > > Is there a LOo guru that has a better idea on how to correct this or how > to do this differently so that it responds even while fetching pics and > such? Maybe there is a setting somewhere I can change to make it work > better. > > Things I've considered but didn't like the results of. Selecting what I > want to print and printing it as a pdf file or just printing directly > without having a copy to edit. For obvious reasons, that doesn't work > well because I sometimes change fonts and sizes for these old eyes. > Doing this in LOo makes things better if I can get it working right. > I've also tried the print friendly version when available but that > removes some things I do want to have, pics mostly. Here are two ideas that won't solve the problem, but might be useful as workarounds: You could try OpenOffice (only available as openoffice-bin?) and see if it works better in that situation. Depending on the web browser you're using (Seamonkey?), you might have an "Inspector" (context menu, "Inspect Element"), which can be used to remove undesired elements. It works when the page is saved (elements which were removed using the inspector are not present in the saved version), hopefully it will also work with copy-paste (but I have never tried to do that). Unfortunately, depending on the web page, the inspector itself can sometimes be slow or even freeze. If you're using Seamonkey as a web browser, here's another idea I didn't try but which might help: ctrl+E will open the current web page for editing in Seamonkey's Composer. -- Nuno Silva
Re: [gentoo-user] how to fix syslog-ng warning about escaped regexp
On Wed, 01 May 2019 07:23:50 -0400, John Covici wrote: > > > Hi. Since my last update I get the following warning when syslog-ng > > > runs: > > > awk: cmd. line:130: warning: regexp escape sequence `\"' is not a > > > known regexp operator > > > > > > I could find nothing at bgo or a google search, so I am wondering if > > > anyone knows how to fix this problem? I am running version 3.20.1 > > > and perl version 5.28.2. > > > > > > Thanks in advance for any suggestions. > > > > I was getting this from the makewhatis cron job in man. The solution > > was to replace man, which is deprecated, with man-db. > > How would this help my problem as I am getting nothing from > makewhatis? What program is producing the log entries? Or is it syslog-ng itself that is doing so? -- Neil Bothwick And on the seventh day God said :wq and then make pgpfpMuit8DAH.pgp Description: OpenPGP digital signature
Re: [gentoo-user] how to fix syslog-ng warning about escaped regexp
On Wed, 01 May 2019 06:03:57 -0400, Neil Bothwick wrote: > > [1 ] > On Wed, 01 May 2019 05:42:17 -0400, John Covici wrote: > > > Hi. Since my last update I get the following warning when syslog-ng > > runs: > > awk: cmd. line:130: warning: regexp escape sequence `\"' is not a > > known regexp operator > > > > I could find nothing at bgo or a google search, so I am wondering if > > anyone knows how to fix this problem? I am running version 3.20.1 and > > perl version 5.28.2. > > > > Thanks in advance for any suggestions. > > I was getting this from the makewhatis cron job in man. The solution was > to replace man, which is deprecated, with man-db. How would this help my problem as I am getting nothing from makewhatis? -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una cov...@ccs.covici.com
Re: [gentoo-user] how to fix syslog-ng warning about escaped regexp
On Wed, 01 May 2019 05:42:17 -0400, John Covici wrote: > Hi. Since my last update I get the following warning when syslog-ng > runs: > awk: cmd. line:130: warning: regexp escape sequence `\"' is not a > known regexp operator > > I could find nothing at bgo or a google search, so I am wondering if > anyone knows how to fix this problem? I am running version 3.20.1 and > perl version 5.28.2. > > Thanks in advance for any suggestions. I was getting this from the makewhatis cron job in man. The solution was to replace man, which is deprecated, with man-db. -- Neil Bothwick Get your copy at http://www.geekthing.com/~robf/gensig/ pgp1OXZftbggH.pgp Description: OpenPGP digital signature
[gentoo-user] how to fix syslog-ng warning about escaped regexp
Hi. Since my last update I get the following warning when syslog-ng runs: awk: cmd. line:130: warning: regexp escape sequence `\"' is not a known regexp operator I could find nothing at bgo or a google search, so I am wondering if anyone knows how to fix this problem? I am running version 3.20.1 and perl version 5.28.2. Thanks in advance for any suggestions. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una cov...@ccs.covici.com
Re: [gentoo-user] udisks and exfat
On Wednesday, 1 May 2019 10:24:02 BST Bill Kenworthy wrote: > Sounds like you are using gnome/systemd ... thats a whole other box of > worms to open. This is a gnomeless openrc system with a recently > getting elogind to replace consolekit. > > > BillK No, that's a can of worms I've consciously stayed away from. ;-) I use openrc with consolekit and Enlightenment or KDE as desktops. Lately I also installed elogind because Skype was asking for it. I checked while logged into KDE and both console-kit-daemon and elogind are running. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] udisks and exfat
On 1/5/19 4:35 pm, Mick wrote: > On Wednesday, 1 May 2019 03:32:21 BST Bill Kenworthy wrote: >> Got sidetracked - turns out fuse and exfat on usb do not play well with >> mounts as a user due to changes late last year. It can now only be >> mounted/unmounted by root. >> >> The second part (also due to fuse) is that to stop fuse (silently as ls >> still showed the execute bit set) from interfering with execution of >> files on the mounted device) it must be mounted as the user under a user >> owned directory such as /home/user (mount cannot deal with this - it did >> in the past, but something has changed). So the solution is to mount >> via root as the user you want (via sudo) under a mount point in the >> users home. This may all be unique to fuse-exfat, and which versions of >> everything involved as I saw one email on the mechanics of the changes >> saying fat is handled a little differently due to a different use >> scenario. And ext2/3/4 etc don't have the problem at all. Auto-mount >> on device plugin still doesn't happen so thats next on my list. >> >> /etc/fstab: >> >> /dev/sda1 /home/myuser/mnt auto >> rw,auto,exec,uid=1000,gid=1000,users,user=myuser 0 0 >> >> >> BillK > exFAT and VFAT are mounted with different permissions by udisks, without > overriding options in fstab or command line. > > A random file in exFAT: > > $ stat /run/media/michael/VERBATIM32G/blah > File: /run/media/michael/VERBATIM32G/blah > Size: 32768 Blocks: 64 IO Block: 4096 regular file > Device: 811h/2065dInode: 19 Links: 1 > Access: (0777/-rwxrwxrwx) Uid: ( 1000/ michael) Gid: ( 1002/ michael) > Access: 2018-06-08 11:20:50.0 +0100 > Modify: 2015-08-24 12:50:56.0 +0100 > Change: 2015-08-24 12:50:56.0 +0100 > Birth: - > > A random file in FAT: > > $ stat /run/media/michael/CRUCIAL-8G/blah > File: /run/media/michael/CRUCIAL-8G/blah > Size: 1731366 Blocks: 3384 IO Block: 4096 regular file > Device: 810h/2064dInode: 124 Links: 1 > Access: (0644/-rw-r--r--) Uid: ( 1000/ michael) Gid: ( 1002/ michael) > Access: 2019-04-08 01:00:00.0 +0100 > Modify: 2007-08-25 22:46:42.0 +0100 > Change: 2019-04-08 14:04:54.0 +0100 > Birth: - > > Ditto for directories. > > exFAT: > > $ stat /run/media/michael/VERBATIM32G/Foo > File: /run/media/michael/VERBATIM32G/Foo > Size: 32768 Blocks: 64 IO Block: 4096 directory > Device: 811h/2065dInode: 24 Links: 1 > Access: (0777/drwxrwxrwx) Uid: ( 1000/ michael) Gid: ( 1002/ michael) > Access: 2018-02-11 17:22:52.0 + > Modify: 2018-02-11 17:22:54.0 + > Change: 2018-02-11 17:22:54.0 + > Birth: - > > > FAT: > > $ stat /run/media/michael/CRUCIAL-8G/Foo > File: /run/media/michael/CRUCIAL-8G/Foo > Size: 4096 Blocks: 8 IO Block: 4096 directory > Device: 810h/2064dInode: 79 Links: 2 > Access: (0755/drwxr-xr-x) Uid: ( 1000/ michael) Gid: ( 1002/ michael) > Access: 2019-04-08 01:00:00.0 +0100 > Modify: 2019-04-08 14:43:26.0 +0100 > Change: 2019-04-08 14:43:26.0 +0100 > Birth: - > > The mount options are different as shown below. > > exFAT: > > $ findmnt -oOPTIONS /dev/sdb1 > OPTIONS > rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other, > blksize=4096 > > FAT: > > $ findmnt -oOPTIONS /dev/sdb > OPTIONS > rw,nosuid,nodev,relatime,uid=1000,gid=1002,fmask=0022,dmask=0022,codepage=437, > iocharset=iso8859-1,shortname=mixed,showexec,utf8,flush,errors=remount-ro > > > In the above examples I used udisksctl to mount the devices. I understand > Gnome expose via Gvfs an API to handle I/O to block devices, which desktop > applications can plug into without performing raw kernel calls to hardware > devices (like e.g. /bin/mount does). I don't run Gnome and am not familiar > with its internals to know how similar it is with udisksctl. > > Regarding mounting with udisksctl I don't know why exFAT and VFAT are > different, but the udisksctl man page provides this revealing information on > the mount permissions allowed: > > The device will be mounted with a safe set of default options. You > can influence the options passed to the mount(8) command with > --options. Note that only safe options are allowed - requests with > inherently unsafe options such as suid or dev that would allow the > caller to gain additional privileges, are rejected. > > HTH. Sounds like you are using gnome/systemd ... thats a whole other box of worms to open. This is a gnomeless openrc system with a recently getting elogind to replace consolekit. BillK
Re: [gentoo-user] udisks and exfat
On Wednesday, 1 May 2019 03:32:21 BST Bill Kenworthy wrote: > Got sidetracked - turns out fuse and exfat on usb do not play well with > mounts as a user due to changes late last year. It can now only be > mounted/unmounted by root. > > The second part (also due to fuse) is that to stop fuse (silently as ls > still showed the execute bit set) from interfering with execution of > files on the mounted device) it must be mounted as the user under a user > owned directory such as /home/user (mount cannot deal with this - it did > in the past, but something has changed). So the solution is to mount > via root as the user you want (via sudo) under a mount point in the > users home. This may all be unique to fuse-exfat, and which versions of > everything involved as I saw one email on the mechanics of the changes > saying fat is handled a little differently due to a different use > scenario. And ext2/3/4 etc don't have the problem at all. Auto-mount > on device plugin still doesn't happen so thats next on my list. > > /etc/fstab: > > /dev/sda1 /home/myuser/mnt auto > rw,auto,exec,uid=1000,gid=1000,users,user=myuser 0 0 > > > BillK exFAT and VFAT are mounted with different permissions by udisks, without overriding options in fstab or command line. A random file in exFAT: $ stat /run/media/michael/VERBATIM32G/blah File: /run/media/michael/VERBATIM32G/blah Size: 32768 Blocks: 64 IO Block: 4096 regular file Device: 811h/2065d Inode: 19 Links: 1 Access: (0777/-rwxrwxrwx) Uid: ( 1000/ michael) Gid: ( 1002/ michael) Access: 2018-06-08 11:20:50.0 +0100 Modify: 2015-08-24 12:50:56.0 +0100 Change: 2015-08-24 12:50:56.0 +0100 Birth: - A random file in FAT: $ stat /run/media/michael/CRUCIAL-8G/blah File: /run/media/michael/CRUCIAL-8G/blah Size: 1731366 Blocks: 3384 IO Block: 4096 regular file Device: 810h/2064d Inode: 124 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 1000/ michael) Gid: ( 1002/ michael) Access: 2019-04-08 01:00:00.0 +0100 Modify: 2007-08-25 22:46:42.0 +0100 Change: 2019-04-08 14:04:54.0 +0100 Birth: - Ditto for directories. exFAT: $ stat /run/media/michael/VERBATIM32G/Foo File: /run/media/michael/VERBATIM32G/Foo Size: 32768 Blocks: 64 IO Block: 4096 directory Device: 811h/2065d Inode: 24 Links: 1 Access: (0777/drwxrwxrwx) Uid: ( 1000/ michael) Gid: ( 1002/ michael) Access: 2018-02-11 17:22:52.0 + Modify: 2018-02-11 17:22:54.0 + Change: 2018-02-11 17:22:54.0 + Birth: - FAT: $ stat /run/media/michael/CRUCIAL-8G/Foo File: /run/media/michael/CRUCIAL-8G/Foo Size: 4096Blocks: 8 IO Block: 4096 directory Device: 810h/2064d Inode: 79 Links: 2 Access: (0755/drwxr-xr-x) Uid: ( 1000/ michael) Gid: ( 1002/ michael) Access: 2019-04-08 01:00:00.0 +0100 Modify: 2019-04-08 14:43:26.0 +0100 Change: 2019-04-08 14:43:26.0 +0100 Birth: - The mount options are different as shown below. exFAT: $ findmnt -oOPTIONS /dev/sdb1 OPTIONS rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other, blksize=4096 FAT: $ findmnt -oOPTIONS /dev/sdb OPTIONS rw,nosuid,nodev,relatime,uid=1000,gid=1002,fmask=0022,dmask=0022,codepage=437, iocharset=iso8859-1,shortname=mixed,showexec,utf8,flush,errors=remount-ro In the above examples I used udisksctl to mount the devices. I understand Gnome expose via Gvfs an API to handle I/O to block devices, which desktop applications can plug into without performing raw kernel calls to hardware devices (like e.g. /bin/mount does). I don't run Gnome and am not familiar with its internals to know how similar it is with udisksctl. Regarding mounting with udisksctl I don't know why exFAT and VFAT are different, but the udisksctl man page provides this revealing information on the mount permissions allowed: The device will be mounted with a safe set of default options. You can influence the options passed to the mount(8) command with --options. Note that only safe options are allowed - requests with inherently unsafe options such as suid or dev that would allow the caller to gain additional privileges, are rejected. HTH. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
